Repository navigation
CI: publish the tag's release directly instead of a draft - #15
Merged
Merged
Conversation
v0.1.0 ended up as two releases: the job's draft (only reachable via an untagged-* URL, with all assets) and a second one published by hand from the tag, with none. Publish on the tag's release instead, updating it in place (assets overwritten) when one already exists; prereleases are never marked latest.
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
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
v0.1.0tag build created a draft release with all six assets. Drafts are only reachable through anuntagged-…URL, so a second release was created by hand from the tag and published, with no assets. That's how the repo ended up with an empty "Latest" release next to a draft holding the files.Change: the release job publishes the tag's release itself (
draft: false). If a release already exists for the tag (made by hand, or from an earlier run),softprops/action-gh-releaseupdates it in place andoverwrite_files: truereplaces its assets, so each tag only ever has one release. Prerelease tags (v*-*) stay prereleases and never getmake_latest.Already fixed by hand for v0.1.0: I uploaded the six assets from the draft to the published release, after checking each against
SHA256SUMSandgh attestation verify. I copied the full notes over and deleted the duplicate draft.Not run yet: the next tag build is the first real run of this path.