Repository navigation
fix(release): cut release notes over GitHub's 125,000 character limit - #236
Merged
Merged
Conversation
…ter limit The first release's notes (all of Unreleased since the start) were 132,954 characters, so publishing v0.4.0 failed. Keep whole entries up to 120,000 and link to CHANGELOG.md at the tag for the rest. The trimming lives in the workflow because the publish job runs release.py as it was at the tag. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01291QUFHs51wLhGQwp2DAh9
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.
Requested by Adeel · project thread
Description
Before: the first release, v0.4.0, was committed and tagged but never published. Its notes were 132,954 characters, and GitHub returned "body is too long (maximum is 125000 characters)" (run).
After: notes over 120,000 characters stop at the last whole entry that fits and end with a link to CHANGELOG.md at the tag.
How: the "Release notes from CHANGELOG.md" step now trims notes.md before publishing. The trimming lives in the workflow, not in release.py, because the publish job checks out the tag and runs the script as it was then. A new dispatch of Release takes its existing resume path and publishes v0.4.0.
Motivation and Context
Unblocks the v0.4.0 release.
Types of changes
Checklist:
🤖 Generated with Claude Code
https://claude.ai/code/session_01291QUFHs51wLhGQwp2DAh9
Generated by Claude Code