Repository navigation
AGENTS.md says what a release asks of the user - #54
Merged
Merged
Conversation
czj
enabled auto-merge (squash)
November 7, 2026 22:34
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.
AGENTS.md said how to release, but not what a release asks of the person running it, nor how to tell that another session had just released: two sessions working on one gem ended up unsure whether a version was out.
This pull request rewrites the Releases section and tightens the rest of the file without dropping anything.
releaseenvironment; check for a release already under way first;--dry-runthen--yes;bin/release --tagafter an interruption; an unsigned tag is never released.