Use one application version across builds and release artifacts #32

New issue

Open

opened 2026-11-01 20:11:49 +00:00 by viacheslavshuka · 0 comments

viacheslavshuka commented

2026-11-01 20:11:49 +00:00

Owner

The production release must identify the same application that passed development validation. A release-preparation pull request sets the final shared SemVer before the image is built.

Scope

Choose one authoritative version source and one update command. Connect backend, frontend, OpenAPI, release tags, and registry release tags to that value.

Acceptance criteria

One documented operation updates the authoritative SemVer and necessary derived files. CI rejects disagreement between backend, frontend, and OpenAPI versions.
A release candidate embeds its final SemVer during development validation. Promotion does not rebuild the image or alter embedded versions.
Environment, commit, and image digest distinguish deployments that share an application version. Diagnostic identity allows deployment checks to reject a healthy wrong build.
Release metadata preserves a permanent mapping from published version to commit and image digest. Published release identity is immutable.
A mismatched release tag or registry tag cannot bind a different artifact to an existing published version. Corrections use a new version.
Conventional Commit titles help draft notes but do not automatically choose a version bump. Version changes remain explicit release-preparation decisions.
Changing release-note wording cannot mutate the release artifact mapping.

Validation

Build a candidate and compare its backend, frontend, OpenAPI, and image identity. Check mismatched version sources, a reused published version, and unchanged identity after promotion simulation.

Dependencies

#10: Generate and verify OpenAPI and the TypeScript client. Version consistency includes generated OpenAPI.
#26: Package and serve the website and API from one image. Version consistency includes the built frontend and image.

#36: Promote published releases without rebuilding their images

The production release must identify the same application that passed development validation. A release-preparation pull request sets the final shared SemVer before the image is built. ## Scope Choose one authoritative version source and one update command. Connect backend, frontend, OpenAPI, release tags, and registry release tags to that value. ## Acceptance criteria - One documented operation updates the authoritative SemVer and necessary derived files. CI rejects disagreement between backend, frontend, and OpenAPI versions. - A release candidate embeds its final SemVer during development validation. Promotion does not rebuild the image or alter embedded versions. - Environment, commit, and image digest distinguish deployments that share an application version. Diagnostic identity allows deployment checks to reject a healthy wrong build. - Release metadata preserves a permanent mapping from published version to commit and image digest. Published release identity is immutable. - A mismatched release tag or registry tag cannot bind a different artifact to an existing published version. Corrections use a new version. - Conventional Commit titles help draft notes but do not automatically choose a version bump. Version changes remain explicit release-preparation decisions. - Changing release-note wording cannot mutate the release artifact mapping. ## Validation Build a candidate and compare its backend, frontend, OpenAPI, and image identity. Check mismatched version sources, a reused published version, and unchanged identity after promotion simulation. ## Dependencies - [#10: Generate and verify OpenAPI and the TypeScript client](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/10). Version consistency includes generated OpenAPI. - [#26: Package and serve the website and API from one image](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/26). Version consistency includes the built frontend and image. ## Related work - [#36: Promote published releases without rebuilding their images](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/36)

viacheslavshuka referenced this issue

2026-11-01 20:11:50 +00:00

Offer a safe reload when an open page needs a new application version #33

viacheslavshuka referenced this issue

2026-11-01 20:11:51 +00:00

Deploy validated main images to development #34

viacheslavshuka added the