Filter PR numbers exceeding GraphQL Int32 bound#51
Merged
RomainCscn merged 1 commit intomainfrom May 5, 2026
Merged
Conversation
A token like #4211934690 in a commit body (e.g. a Cursor Bugbot review id) was extracted as a PR number and sent to the release sync mutation. Linear's API types pullRequestReferences[].number as Int (signed 32-bit), so the mutation was rejected and the release pipeline got stuck — every subsequent push re-included the offending commit because the last released SHA never advanced. Drop any extracted #NNN that exceeds 2^31-1 across all three extraction paths (squash / merge / message-scan fallback) and log the skip at verbose level.
axelniklasson
approved these changes
May 5, 2026
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
2 participants
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
extractPullRequestNumbersForCommitscans commit messages for#NNNand forwards each aspullRequestReferences[].numberon the release sync mutation. That field is a GraphQLInt(signed 32-bit), so any token above 2,147,483,647 fails the entire mutation.A real-world example: a commit body containing a Cursor Bugbot review id (
#4211934690) overflows the bound. BecausegetLatestSha()only advances on a successful release, every subsequent push re-includes the same commit and the pipeline stays stuck.Change
MAX_PR_NUMBER = 2_147_483_647and apushIfValidhelper inextractors.ts.verboselog explaining why.Tests cover the cursor reproducer, mixed valid+oversized in the fallback, oversized in squash and merge formats, and the boundary (
2^31-1accepted,2^31dropped).