Repository navigation
fix(tools): Explain update_issue's inRelease rejections - #2363
Merged
Merged
Conversation
An agent resolving issues lost seven calls to two update_issue errors that did not say how to recover: - `resolvedInNextRelease` with `inRelease` got "can only be used when `status` is `resolved`". It now says that resolvedInNextRelease picks the release itself, and to drop inRelease or use `resolved`. - A short release name such as `v1.2.3` passed through Sentry's raw 400, "Unable to find a release with the given version". Sentry matches the stored version exactly, so update_issue now says to pass the full version from find_releases, and that the issue did not change. The inRelease description now asks for the full version too.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
update_issue now tells agents to copy inRelease from find_releases, and Sentry matches inRelease against the stored version exactly. find_releases returned shortVersion, which the API schema allows to be shorter than version, so return version instead.
MathurAditya724
approved these changes
Nov 18, 2026
MathurAditya724
left a comment
Member
There was a problem hiding this comment.
Verified release validation against Sentry status_details.py and resolution logic. All 63 update_issue and find_releases tests pass, including exact stored release versions and unrelated validation errors. Earlier recovery-guidance finding is addressed. No blocking issues found.
This branch was successfully deployed
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.
An agent resolving issues lost 7 calls to two
update_issueerrors that didn't say how to recover (MCP-SERVER-GRX, see #2362):status: "resolvedInNextRelease"+inReleasegot "inReleaseandinCommitcan only be used whenstatusisresolved". The rejection is right, but the agent read it as a schema bug. It now says thatresolvedInNextReleasepicks the release itself, and to dropinReleaseor useresolved.v5.7.58forpkg@v5.7.58-<sha>+273) passed Sentry's raw 400 through:{"statusDetails":{"inRelease":["Unable to find a release with the given version."]}}. Sentry matches the stored version exactly (getsentry/sentrysrc/sentry/api/helpers/group_index/validators/status_details.py:104-111).update_issuenow turns that field error into aUserInputErrorthat says to pass the full version fromfind_releasesand that the issue didn't change. Other 400s pass through unchanged.inReleasedescription now asks for the full version, asfind_releasesreturns it.find_releasesnow returnsversioninstead ofshortVersion, so copying from it always gives the exact version. Current Sentry sends the same value for both, but the API schema allowsshortVersionto be shorter.The parsing follows
getSeatErrorReasoninupdate-uptime-monitor.ts, since the API client keeps a field error's body only as text indetail. Nothing breaks: the changes are error text, one parameter description, andfind_releasesreturning the full version string.Refs #2362
via automation
evt_905b9c478746fd9deeb853f85ad7441b· Run IDdispatch_728b24ef5cfba761b02ae3da7730c93a.--
View Session [Sentry]