[sentry-junior]

Adds idempotent: boolean to every ApiOperation in @sentry/api/operations. Retrying clients such as the CLI and MCP can then decide from the catalog whether to resend a request after a timeout or 5xx, instead of hard-coding that per call site.

Refs getsentry/sentry#128927. The Sentry side, getsentry/sentry#128930, now stamps x-sentry-idempotent: true on operations whose endpoint declares the method in idempotent_methods.

Semantics

• GET, HEAD, OPTIONS, TRACE: always true (RFC 9110 §9.2.1). Clients get one field to check, with no method special-casing.
• Other methods: true only when the operation has x-sentry-idempotent: true. PUT and DELETE are not assumed idempotent because not every Sentry handler follows RFC 9110 §9.2.2. Sentry makes the same choice.
• false means "not known to be idempotent", not "known to be unsafe". It is documented that way in the type docs and the README.

Current effect

Today's openapi-derefed.json has no x-sentry-idempotent markers. The endpoints declared so far (chunk upload, DIF assemble, artifact bundle assemble) are all PRIVATE, so nothing non-safe is marked yet. In the current build, 147 of 266 operations are idempotent: true, all safe methods. Non-safe operations will be marked as they're published with the declaration.

Verification

• bun run build, bun run typecheck, bun test (167 pass), bun run test:node
• New test: a marked POST is true; an unmarked POST/PUT/DELETE is false. Existing catalog fixtures assert true for GET and false for an unmarked POST.

via BYK.

--

View Junior Session in Sentry