docs: add pre-release requirements section - #113
Merged
Conversation
skjnldsv
force-pushed
the
docs/pre-release-requirements
branch
from
August 26, 2026 08:55
a30868f to
0622c90
Compare
Assisted-by: ClaudeCode:claude-opus-4-8 Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
skjnldsv
force-pushed
the
docs/pre-release-requirements
branch
from
August 26, 2026 08:56
0622c90 to
0181ab0
Compare
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.
Adds a Pre-release requirements checklist to the README: release schedule current, per-major config JSON present, and version bump PR merged on server. Also notes the release is triggered by the legacy release script, not by hand.
AI-assisted change (Claude Code); authored and reviewed by me.