docs: record the GHCR cutover as done - #23
Merged
Merged
Conversation
Production runs sha-469337c from the registry as of 2026-09-21. Records the deployed tag, the fallback image kept for rollback, and the checks that proved the cutover was content-neutral, so the next deploy has a known starting point instead of having to rediscover one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #22, which changed
compose.prod.ymlbut could not state what was actually deployed.Production now runs
ghcr.io/voltiusapp/voltius-server:sha-469337cfrom the registry, deployment tree atbfd0f9a,SERVER_TAGset in.env.dockhand, and the last locally built image kept asvoltius-server:pre-ghcr-20260921for rollback.The cutover was content-neutral by design — same commit as the binary that was already running, verified by comparing
stringsoutput before recreating. No migration ran./health,/v1/billing/subscriptionand/v1/teamsreturned 200, 401, 401 locally and through the tunnel.Recording the deployed tag in the runbook means the next deploy starts from a known state rather than inspecting the container to work out where it is.