Sentry breaking change: POST /api/0/organizations/{organization_id_or_slug}/releases/
Validated schema comparison changed the request accepted instance set.
Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.
Which field and classification rule changed?
- Changed field
Operation-level change- Rule ID
schema.request_acceptance_narrowed- Classifier version
2026-10-15.2- Direction
- request
- Finding ID
chg_079541d52df7270986502b342d237f71f252c6a2cfda2268f1caba1235b4abcc
What is the recorded before and after evidence?
Previous specification SHA-256: 0689f5be1685af4feae84005801b76f26e5ff34f6f7b13178e76891caeaa2a98
Revised specification SHA-256: d65ffb6f342436ad29ca5416d88fc3e2b0ff096602b08ab18154c0a6f818ab18
Publisher version: v0 to v0.
...
projects:
description: A list of project slugs that are involved in this release.
- items: {}
+ items:
+ type: string
type: array
ref:
...Inspect the complete release · Public source findings · Publisher specification source
How do I check whether this affects my code?
Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.
Check an authorized repository · Review coverage · Inspect classification rules