feat: publish tagged images via metadata-action #39
Conversation
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
wietzesuijker
force-pushed
the
feat/release-tagging-ci
branch
from
88b4246 to
a1cdd64
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
CI relies on manual YAML edits before releases, only pushes
main/latest, skipspr-*and semver tags, and has no guardrails to ensure we tag from a clean, up-to-datemainor visibility into what shipped. This change automates tag publication, adds release safety checks, and summarizes the published tags.What
docker/metadata-action@v5, yielding branch, PR, SHA, and semver (vX.Y.Z,vX.Y,vX) tags automatically and emitting a tag summary in the workflow run.make releasehelper (scripts/tag_release.sh) that insists on a clean, syncedmain, semantic tag names, and allows an opt-in--forceretag.workflows/README.mdso the default flow stays “merge + make release,” with clear steps for pinning environments to the new tag when required.