ci(release): draft a GitHub release alongside the GHCR push - #4
Open
starvy wants to merge 1 commit into
Open
Conversation
The tag push already published the image but left no release, so there was nothing for users to read or subscribe to. Draft, not published: the notes are generated and unreviewed, and a draft is the last point a bad tag can be walked back before an announcement goes out.
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.
The
v*tag workflow published the image to GHCR but left no GitHub release, so a tag produced nothing users could read or subscribe to.Adds a
releasejob gated onneeds: image— the draft only appears once the image it advertises is actually pullable. The body is composed here (pull instructions, then the API-generated changelog) rather than via--generate-notes, so ordering is explicit.v0.1.0-rc.1) is marked prerelease, matching metadata-action'slatest=auto— so the release and thelatestimage tag agree on what counts as a real release.packages: writemoved off the workflow root onto theimagejob;releasetakescontents: write.Ready for
git tag v0.1.0 && git push --tags.