release: rename v0.1.0 to v0.1.1 in CHANGELOG - #58
Merged
Merged
Conversation
v0.1.0 can never be published on this repo: GitHub's Immutable
Releases feature permanently blocks reusing a tag name once it has
been published, even after deletion ("tag_name was used by an
immutable release"). The original v0.1.0 tag/release was deleted
after its container-image path failed mid-pipeline (docker-sign's
SBOM attestation 403, fixed at attested-delivery/.github#32 and
1c54125/60cd658 in this repo) — since it can't be reused, this
version becomes v0.1.1 instead, with a Fixed entry documenting why.
There was a problem hiding this comment.
Pull request overview
Updates the project’s release history documentation to reflect that v0.1.0 cannot be republished due to GitHub Immutable Releases, and prepares the next publishable release as v0.1.1 with the relevant container/SBOM pipeline fix noted.
Changes:
- Renamed the
0.1.0changelog section to0.1.1for the 2026-07-13 release. - Added a “Fixed” entry documenting the upstream SBOM upload permissions fix impacting tagged container releases.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
v0.1.0can never be published on this repo: GitHub's Immutable Releases feature permanently blocks reusing a tag name once it's been published, even after both the tag and release are deleted (tag_name was used by an immutable release, confirmed viagh release createreturning HTTP 422 forv0.1.0). This actually matches the org's own governance principle that a release's identity is immutable — GitHub is enforcing it at the platform level.This renames the changelog's
[0.1.0]section to[0.1.1]and documents the container-pipeline fix (#57, upstream attested-delivery/.github#32) as aFixedentry, so the next tag (v0.1.1) ships a complete, fully-attested release including the container image.Verification
just checkpasses clean (build+lint+test, via pre-push hook).