Repository navigation
ci(release): trim release to tag name and binaries - #4
Merged
Merged
Conversation
The release is now named after the tag alone. The whole annotated tag message becomes the body, so the annotation no longer carries a title line for the name to be taken from. checksums.txt goes. It guarded nothing here: it shipped from the same job, in the same release, over the same transport as the binaries it attested, so anything able to replace an asset could replace the list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 #3, before the workflow has published anything.
What changed
The release name is the tag and nothing else —
v0.2.0, not a tag subject line promoted into a title. The whole annotated tag message becomes the body now, so the annotation no longer needs a title line, andCLAUDE.md's tagging example starts straight at the first**Section**.checksums.txtis dropped. It guarded nothing: it was generated in the same job, attached to the same release, and served over the same transport as the binaries it attested. Anything able to replace an asset could replace the list alongside it. A checksum file is worth having when it is signed or published somewhere the artifacts are not, and neither applies here.The Linux artifact keeps its lack of an extension — an ELF is executable by its mode bit, so
semibase_<version>_linux_amd64is the correct name. Now stated in the code comment and inCLAUDE.mdso it does not read as an oversight.Verified
GITHUB_OUTPUTwith its blank lines and bold section labels intact.Release <tag>; the%(objecttype)guard is unchanged.nameinput resolves tosteps.tag.outputs.tag.