ci(release): create the GitHub Release the tag needs - #1
Merged
Merged
Conversation
A tag is not a release. The repository page, the Releases sidebar and `/releases/latest` all read the Release object, so a tag pushed without one leaves the front page advertising an older version — v1.2.0 was tagged and its images published on 2026-09-01, and the page kept offering v1.1.1 until the release was created by hand. Runs after both image jobs, so a release never points at a version that cannot be pulled yet, and carries the same newest-tag guard they do: re-cutting an older tag gets its own release, but does not take "Latest" from a newer one. An existing release is left untouched — hand-written notes are the house style and a re-run must not overwrite them; generated notes are only the floor for a tag that would otherwise have no release at all.
|
Thank you for your contribution to @imqueue. Before this pull request can be merged, please read the @imqueue Contribution Terms and sign them by posting the following comment exactly: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
v1.2.0was tagged on 2026-09-01 and its images published, but no GitHub Release object was created — releases here are cut by hand. The repository page, the Releases sidebar and/releases/latestall read that object, not the tag list, so the front page kept advertisingv1.1.1. The v1.2.0 release has now been created manually; this stops it recurring.Adds a
github-releasejob that runs on a tag push, after both image jobs, so a release never points at a version that cannot be pulled yet.publishandlatest: re-cutting an older tag gets its own release, but--latest=falsekeeps "Latest" on the newer one.workflow_dispatch, where the ref is a branch.