When a Sentry OpenAPI query value disappears

Soumik Ghosh — Sat, 14 Nov 2026 12:27:03 +0000

A small query enum can carry an important compatibility guarantee. Sentry's captured replay-list specification removed info_ids from the allowed items in its field query parameter. The method and endpoint are still present in this finding. A request that sends the removed value falls outside the revised contract.

GET /api/0/organizations/example/replays/?field=info_ids

Start at the place the query is assembled. The value may come from a literal, a user-selected field list, or a shared SDK wrapper. Search for info_ids and check the code that picks and serializes the values. A string search is a starting point because the caller can build the query at runtime.

The diff does not select a replacement. First find out what the application does with the information. If the result is optional, omitting the field might be appropriate. If it drives a workflow, identify an officially supported source for the data and test the new request and response together.

The captured finding records the changed constraint and the exact compared revisions. A capture documents what changed in the published contract. Runtime behavior needs separate verification.

Disclosure: This cross-post was generated by an AI agent from the original ParityDiff teardown.

An optional OpenAI response field can break an existing caller

Soumik Ghosh — Sat, 14 Nov 2026 12:26:20 +0000

A response change can break callers even when the provider removes no endpoint. In a captured OpenAI specification revision, the URL on a web-search find action stopped being required. The contract now permits a result without that field. A client that passes the URL straight into a parser can fail when it receives that result.

A TypeScript cast can hide this assumption. If an application casts the result to a type whose URL is required, the compiler will accept a subsequent read. Check the runtime value before parsing it and decide what the application should do when the URL is missing.

if (typeof action.url === 'string') {
  inspectSearchUrl(action.url);
} else {
  handleMissingSearchUrl(action);
}

The fallback depends on the caller. A renderer might leave the link out. A workflow that requires a link might need to stop and report an incomplete result. Add a fixture for both responses and confirm the behavior with the SDK version the application actually uses.

The captured finding shows the underlying operation, classifier rule and compared revisions. The capture documents a change to the specification. It does not establish when a production service began returning the field optionally.

Disclosure: This cross-post was generated by an AI agent from the original ParityDiff teardown.

DEV Community: Soumik Ghosh

When a Sentry OpenAPI query value disappears

An optional OpenAI response field can break an existing caller