fix: increase maxOutputTokens to prevent PR description truncation #126
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
- Increase maxOutputTokens from 8192 to 16384 tokens - Update prompt to guide AI to be more concise - Add guidance to use bullet points and group similar changes - Prevents release descriptions from being truncated mid-sentence The 8192 token limit (~32KB) was too small for comprehensive release descriptions, causing truncation like 'incremented from `3' instead of 'incremented from `3.22.0` to `3.23.0`'.
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.
Summary
maxOutputTokensfrom 8192 to 16384 tokens in the auto-release-description actionProblem
The current release PR for rsm-monorepo (v3.23.0) has a truncated description:
The text cuts off at "from
3" instead of completing "from3.22.0to3.23.0`".Root Cause
The
maxOutputTokenslimit was set to 8192, which is approximately 32KB of text. When the Gemini API generates comprehensive release descriptions, it hits this limit and truncates the output.Solution
Testing
Tested locally with the rsm-monorepo release/v3.23.0 branch diff and confirmed the script generates complete output without truncation.
Impact
Once merged to
main, this will automatically fix future release PR descriptions since the workflow uses@mainbranch.