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.
Top comments (0)