AccelerUpDocs
Delivery/Deployments/Releases and changelogs

Releases and changelogs

What shipped, per environment, with notes people actually read.

A release is a version of a service, tracked from the first environment it reaches to the last.

The release page

VersionThe tag
ChangesetCommits and pull requests
EnvironmentsWhere it is now, and when it got there
HealthThe score per environment
ContributorsWho is in it
IssuesLinked Jira issues

Release notes

Notes are generated from the changeset and posted to Slack per environment.

Conventional-commit prefixes (feat:, fix:, chore:) are grouped automatically. A repository that uses them gets structured notes for free; one that does not gets a flat list, which is still better than nothing.

AI-drafted changelogs

The Copilot can draft a human-readable changelog from the changeset — grouping related commits and writing what changed in prose.

Important

A draft. It can tell you what the commits did; it cannot know why it mattered or what it means for the reader. Read it before it goes out — the notes are read by people outside your team.

Export as markdown with Copy.

Announcing to pull requests

When a release goes to production, AccelerUp can comment on the pull requests it contains: "shipped in 4.18.2, production, 2026-09-15".

This closes a loop that is otherwise always open — the author of a PR merged three weeks ago has no idea whether it is live.

The weekly digest

A weekly digest of everything released, posted to a configured Slack channel. Set the environment name release-digest in the notification settings.

Reverting

A release can be reverted from here. It creates a new deployment with the previous version and is tracked as its own release, not as an erasure.

Where this behaviour lives: backend/internal/worker/release_sync_worker.go, frontend/src/app/deployments/releases/. If the code and this page disagree, the code is right — please fix the page.

Part of DeliveryDeployments, pipelines, releases and everything that ships code.