chore: release 0.1.1 - #16
Merged
Merged
Conversation
v0.1.0 was tagged but never published: its release run failed in the first job on the git cat-file tag check, fixed in #12. Nothing reached any registry. Re-tagging v0.1.0 would have been tidier, but the Immutable release tags ruleset refused the deletion -- for me too, since it has no bypass actors. That control exists precisely to stop a published version tag being moved, and weakening it to correct a version number in a repository whose whole point is supply-chain rigour would be the wrong trade. So the tag stays, pointing at a commit that was never released, and 0.1.1 becomes the first published version. The changelog records why 0.1.0 does not exist on any registry, so nobody has to reconstruct it from workflow logs later. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CEdTd43qLEEE5qCsL1A7gW
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Bumps all three manifests to
0.1.1and records why0.1.0will never exist on a registry.Why not just re-tag 0.1.0
v0.1.0was tagged but never published — its run failed in the first job on thegit cat-filetag check, fixed in #12. Nothing reached npmjs, PyPI or Packagist.Deleting and re-tagging would have been tidier. The
Immutable release tagsruleset refused it, for me as well, since it has no bypass actors:That control exists precisely to stop a published version tag being moved. Weakening it to correct a cosmetic version number, in a repository whose entire point is supply-chain rigour, is the wrong trade. So
v0.1.0stays as a tag pointing at a commit that was never released, and0.1.1becomes the first published version.Mildly satisfying that the first real test of that ruleset was it telling me no.
After merging
I'll tag
v0.1.1. The run will build and attest, then pause for your approval on thereleaseenvironment before anything is published — that gate can't be satisfied by me.