Repository navigation
Release guard: only v1.1.* tags on 1.1 - #74
Merged
Merged
Conversation
v1.1.5 was created in the GitHub release form with its default target
main. Besides the branch, the release job now checks the tag against
RELEASE_TAGS ("v1.1.*") before attesting and uploading the PHAR (main
accepts only v2.* tags, #73).
AGENTS.md: create tags with git tag, never in the release form; mark
1.1.x as "Latest" by hand before 2.0.0 exists; note on v1.1.5
(soft-deleted on Packagist, replaced by v1.1.6).
Co-Authored-By: Claude Opus 5.5 <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
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.
1.1: besides the branch, check the tag againstRELEASE_TAGS(v1.1.*) before attesting and uploading the PHAR. Counterpart of Release guard: only v2.* tags on main; release plan for 1.1.6/1.1.7 #73 (v2.*onmain).git tag, never in the GitHub release form (target defaults tomain, which is how v1.1.5 ended up onmain); mark 1.1.x as "Latest" by hand before 2.0.0 exists; note on v1.1.5 (soft-deleted on Packagist, replaced by v1.1.6).Merge this before tagging v1.1.6, so the release of v1.1.6 already runs the new check.
🤖 Generated with Claude Code