Skip to content

chore(docs): add changelog and document release process - #297

Merged
sabinem merged 3 commits into
mainfrom
chore/release-process
Sep 10, 2026
Merged

chore(docs): add changelog and document release process#297
sabinem merged 3 commits into
mainfrom
chore/release-process

Conversation

@sabinem

@sabinem sabinem commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

This PR provides:

  • CHANGELOG.md: Keep a Changelog, hand-maintained, entry written in the PR that makes the change. [0.8.0] summarises what's in production today.
  • just version::bump: rolls [Unreleased] into a dated heading for the version being cut, so release notes can't be forgotten on release day.
  • RELEASING.md: that merges reach the running app; how to check what an instance serves (footer, or digest comparison); how to deploy deliberately; how to pin or roll back to an immutable - tag; the three version numbers; how to cut a release and make it deployable.
  • README.md / CLAUDE.md: pointers, plus a new invariant for the deploy-on-restart behaviour.

The repo had no changelog, so the only account of what a release
contains was the commit messages.

Keep a Changelog format, hand-maintained, one line per PR. The 0.8.0
entry summarises what is in production rather than reconstructing it
commit by commit; it predates the file and says so.

Deliberately not generated from commit messages.
A hand-maintained changelog rots the moment someone forgets to move
[Unreleased] on release day. bump now lifts whatever sits under that
heading into a dated heading for the version being cut, and leaves
[Unreleased] empty again — so a version's notes are exactly what was
written while it was being built.
RELEASING.md describes the current release process and what happens
if a feature is merged to main. It also decribes the branching model
and the versioning of App and Charts.
@sabinem
sabinem merged commit 3c9856a into main Sep 10, 2026
6 checks passed
@sabinem
sabinem deleted the chore/release-process branch September 10, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant