changelog.sgen.com is now live

April 22, 2026. Every shipped change now has a public, dated entry at changelog.sgen.com. Read the release ledger, follow the cadence, see what's been improving week by week.

What's there

The Changelog is the public record of platform changes — features added, fixes shipped, behavior tightened. Each entry has:

• Date — the day the change went live
• Title — a customer-readable summary
• Detail — what changed and what to expect
• Cross-reference — link back to the relevant docs page when applicable

The ledger goes back to the first day of platform work and forward through every release cycle.

How to read it

Two reading modes are supported:

• Roadmap Changelog — features and fixes you can see, written in customer-readable language. The default view.
• Maintainer Changelog — full technical detail with file paths, migrations, and implementation notes. For teams who want the engineering depth.

Both modes cover the same shipped changes. The Roadmap view is shorter and sharper; the Maintainer view goes deeper for engineers who want it.

Per-product feeds

Changelog entries are organized by product surface:

• SGEN App — the CMS, the visual builder, and the admin surface
• SGEN Dashboard — the account-level cockpit at dashboard.sgen.com

Each surface has its own feed. If you only care about admin-side changes, read the SGEN App feed. If you manage multiple sites and care about the Dashboard, read that feed separately.

Why publish a changelog

Three reasons drive the public changelog:

Transparency. Customers and prospects can see what's shipping and at what cadence. No "trust us, the platform is improving" — read the ledger.

Coordination. Teams that depend on SGEN can plan around feature timing. If a release lands that changes a behavior you depend on, the changelog is the place to find out.

Accountability. A public changelog is a forcing function for shipping. When every change is dated and published, the question "what changed this week" has a public answer.

The cadence

SGEN ships multiple times a week. The changelog absorbs that cadence — some days have one entry, some have five or six. The entries land within a day of the change going live.

The newest entry sits at the top. Older entries scroll into history. The full ledger is paginated; the home page shows the most recent batch.

What counts as a changelog entry

Anything that's customer-visible and not a private internal change:

• A new feature lands
• A behavior changes (a default flips, a flow shortens, a limit moves)
• A bug fix that customers noticed
• A reliability or performance improvement that's measurable
• A documentation surface goes live

Things that don't make the changelog: internal refactors invisible to customers, security work being kept quiet until coordinated disclosure, beta-tier features that aren't public yet.

How the Changelog connects to the docs

The Changelog is the dated ledger. The docs at docs.sgen.com are the steady-state reference. They cross-link:

• Each changelog entry links back to the Reference or Guide page that documents the feature
• Each Reference and Guide page links forward to changelog entries that affected its current state

If you read a docs page and want to know when a behavior was added, follow the changelog link. If you read a changelog entry and want the full feature spec, follow the docs link.

How to subscribe

The Changelog ships an RSS feed. Add changelog.sgen.com/rss to your feed reader and updates land in your queue. No email signup, no account required, no marketing list.

The Changelog also exists as a JSON feed at the same path — useful for teams that pull SGEN release data into internal dashboards.

What's next

A few items in flight that aren't in today's launch:

• Filtering by tier — read only Launch entries, or only Bug Fix entries, or only Performance entries.
• Per-feature subscription — get notified only when entries that mention a specific feature ship.
• Customer-facing search — full-text search across every changelog entry.

For today, the ledger is open and the cadence is real. Read it, subscribe to it, plan around it.

Next steps

• Open changelog.sgen.com and skim the most recent entries.
• If you depend on a specific feature, scroll back to the date you last reviewed and read forward.
• If you write internal docs that reference SGEN, bookmark the per-product feed that matches your audience.