Repository navigation
docs: prepare v5.3.1 release - #152
Merged
Merged
Conversation
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.
Prepare the maintenance release after v5.3.0-gs.1 as v5.3.1, following the accepted plain-semver ADR. Update the install pin, record the fixture fix and maintenance changes with compatibility/platform boundaries, and document the existing source-only release procedure.
Validation: task docs-check and git diff --check passed. The full release gate, workflow validation, and secret scan will run on the exact merged release candidate before tagging; the tag workflow must pass before the GitHub Release is published.