Skip to content

fix(tools): Explain update_issue's inRelease rejections - #2363

Merged
MathurAditya724 merged 2 commits into
mainfrom
fix/update-issue-in-release-errors
Nov 18, 2026
Merged

MathurAditya724 merged 2 commits into
mainfrom
fix/update-issue-in-release-errors

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

An agent resolving issues lost 7 calls to two update_issue errors that didn't say how to recover (MCP-SERVER-GRX, see #2362):

  • status: "resolvedInNextRelease" + inRelease got "inRelease and inCommit can only be used when status is resolved". The rejection is right, but the agent read it as a schema bug. It now says that resolvedInNextRelease picks the release itself, and to drop inRelease or use resolved.
  • A short release name (v5.7.58 for pkg@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/sentry src/sentry/api/helpers/group_index/validators/status_details.py:104-111). update_issue now turns that field error into a UserInputError that says to pass the full version from find_releases and that the issue didn't change. Other 400s pass through unchanged.
  • The inRelease description now asks for the full version, as find_releases returns it.
  • find_releases now returns version instead of shortVersion, so copying from it always gives the exact version. Current Sentry sends the same value for both, but the API schema allows shortVersion to be shorter.

The parsing follows getSeatErrorReason in update-uptime-monitor.ts, since the API client keeps a field error's body only as text in detail. Nothing breaks: the changes are error text, one parameter description, and find_releases returning the full version string.

Refs #2362

via automation evt_905b9c478746fd9deeb853f85ad7441b · Run ID dispatch_728b24ef5cfba761b02ae3da7730c93a.

--

View Session [Sentry]

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.
@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
sentry-local Skipped Skipped Nov 18, 2026 11:52am UTC

Request Review

Comment thread packages/mcp-core/src/schema.ts Resolved
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 MathurAditya724 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@MathurAditya724
MathurAditya724 marked this pull request as ready for review November 18, 2026 18:28
@MathurAditya724
MathurAditya724 requested a review from a team as a code owner November 18, 2026 18:28
@github-actions github-actions Bot added the risk: medium PR risk score: medium label Nov 18, 2026
@MathurAditya724
MathurAditya724 merged commit 0f38f75 into main Nov 18, 2026
36 checks passed
@MathurAditya724
MathurAditya724 deleted the fix/update-issue-in-release-errors branch November 18, 2026 18:28

This branch was successfully deployed

1 active and 1 inactive deployments
Actions — 305fa4a6 Deployed Nov 18, 2026 by sentry-junior[bot] via eval #1958
Preview — 305fa4a6 Deployed Nov 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium PR risk score: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant