Repository navigation
Document how a release is made - #41
Merged
Merged
Conversation
Describe the release procedure: developer-initiated, prepared through a release pull request, annotated tag and GitHub release by the developer, and the follow-up work after a release.
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
The procedure follows how the twelve releases so far were made (a release commit that only changes
CHANGELOG.md, anX.Y.Ztag withoutv, a GitHub release, Packagist through its webhook), with the changes agreed with the maintainer:Evidence
After: the steps with a completion criterion each, and
AGENTS.mdpoints to them.Merge Danger
Door: two-way
Blast Radius: none
Documentation only. It states that a release is never started by an agent.