Repository navigation
Fix release bodies exceeding GitHub's size limit - #87
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.
The v0.2.49 release job rendered the complete historical release-notes document into a 125,588-character GitHub release body, exceeding GitHub's 125,000-character limit.
Select the exact tagged version section, preserve its full prose and tag-bound documentation links, and append a link to the complete release history. Headings inside Markdown fences cannot select or end a version section. Missing or duplicate versions fail before an output file is created. The v0.2.49 body is now 1,345 characters without truncation.
Validation: 25 release/distribution tests and 36 subtests pass; strict mypy passes for the generator; Ruff and formatting pass for both changed files. Existing release tags and distributions are unchanged. Publication of the retained v0.2.49 artifacts remains a separate operation.