Skip to content

docs: document dev image promotion policy #474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
weicao merged 1 commit into from
Aug 22, 2026
Merged

docs: document dev image promotion policy #474

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions docs/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,13 +89,14 @@ Independent acceptance must cover startup, MySQL and PostgreSQL queries,
initialization scripts, persistent data, and restart recovery. Record the test
report or task reference before promotion.

Only an accepted release candidate may become stable. Run the **Promote
Image** workflow from the `main` branch with:
Only an accepted immutable development build or release candidate may become
stable. Run the **Promote Image** workflow from the `main` branch with:

- the full source SHA;
- the existing release-candidate version;
- the existing immutable development or release-candidate version;
- the accepted `sha256:...` digest;
- the new stable version;
- the explicit stable `vX.Y.Z` version (which may have a different prerelease
base when that product version change is intentional);
- the independent acceptance reference.

The workflow verifies that the source commit is reachable from `main` and that
Expand All @@ -107,9 +108,11 @@ including the workflow run, per-platform digests, acceptance reference, and
previous `latest` digest.

For example, after accepting `v0.1.0-rc.1`, promote its existing digest to
`v0.1.0` and `latest`. The immutable image still reports its original build
version (`v0.1.0-rc.1`); the stable tag records that this exact candidate passed
release acceptance.
`v0.1.0` and `latest`. For a development build that includes a deliberate
product-level compatibility boundary, after accepting
`v0.1.0-dev.20260822.3`, promote the same digest to `v0.2.0` and `latest`.
The immutable image still reports its original build version in either case;
the stable tag records that this exact candidate passed release acceptance.

## Roll back `latest`

Expand Down
Loading