Repository navigation
Standardize releases for the fresh baseline - #21
Merged
Merged
Conversation
ryanbarlow97
force-pushed
the
codex/consistent-release-presentation
branch
from
September 22, 2026 21:47
b11072b to
d1ef344
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.
Release pages mixed tag-only titles, project-name titles, and differently structured notes. Generate exact-tag titles with consistent Changes and Downloads sections, including links to the uploaded artifacts, checksums, and build metadata.
Document the same convention for manual publication and initial source releases.
Validation: shell and embedded Python syntax; executed the actual notes formatter against JAR and archive fixtures; git diff --check.
Documentation link/navigation checks and all five checker unit tests passed.