# Releases

> Versioned shipping bundles with AI-generated release notes, channel targeting, and a public changelog when you want one.

Source: https://productos.ca/documentation/pages/golden-thread/releases (last reviewed 2026-09-22)

A Release bundles features that ship together. Versioned, dated, optionally public.

## What you'll see

- **Lifecycle strip**: draft / planned / in progress / shipped / published counts above the table; click a node to narrow to it
- **List view**: title, ID, status, date, sprint, linked features, other changes, channels, targeting, initiatives, version, description; sorted by date, newest first
- **Filter bar**: status (`draft | planned | scheduled | in-progress | shipped | published`), release date

## Row drawer

- **Scope**: the features this release ships, one row each with live status, progress and assignee, plus a shipped count and average progress for the release. Link a feature from the search at the bottom of the table.
- **Other changes**: free-text lines for work that shipped but isn't tracked as a feature ("Fixed crash when exporting to CSV"). Press Enter to add the next line. Typing a feature's title here doesn't link the feature; use the scope table.
- **Release notes**: rich-text editor, stored as Markdown
- **AI-generated notes**: draft generated from the linked features and other changes (one-click accept or edit)
- **Channels**: changelog / widget / email checkboxes, plus a free-text **Targeting** audience (defaults to `All users`)
- **Initiatives**: the initiatives this release ships against
- **Public flag**: `is_public` is set through the API or an AI action; there's no toggle in the drawer

## Common actions

- Entity-context shortcuts apply once a row has focus (see [Keyboard shortcuts](https://productos.ca/documentation/pages/settings/keyboard))
- **Draft with ProductSense** on the Notes field: ProductSense drafts release notes from linked features and other changes
- **Publish** (new releases only): saves the draft as a real release; needs a title and a version. It doesn't change the status field.

`G R` jumps to Releases from anywhere (`G P` goes to the Roadmap).

## Release status

You set a release's status yourself. It doesn't change when its features ship, and changing it doesn't move them. The shipped count and average progress in the scope table show whether the work is actually done.

## Sprint pill

Each release row carries a sprint pill showing the sprint window its date falls inside (e.g. `Sprint 12`). Sprint windows are computed from the workspace [Sprint Cadence](https://productos.ca/documentation/pages/settings/overview); releases without a date show no pill.

## Public changelog

The public changelog is off by default and has no Settings toggle yet; an owner or admin switches it on through the API or the MCP action described in the [Settings overview](https://productos.ca/documentation/pages/settings/overview). Once it's on, releases with `is_public = true` and a status of `scheduled`, `published` or `shipped` appear at `productos.ca/changelog/{workspace-slug}`: no auth required for visitors. Notes render as plain text with line breaks preserved, newest date first.

## Related

- [Releases API reference](https://productos.ca/documentation/api/v1/reference/releases)
- [Launch Plans](https://productos.ca/documentation/pages/gtm/launches): coordinates the GTM side of a release
- [Outcomes page](https://productos.ca/documentation/pages/golden-thread/outcomes): recorded after a release publishes
