The following repositories use one of the schemas you are editing. It is recommended to roll out schema changes in small PRs, meaning that if those used versions lag behind the latest, it is probably best to update those services before rolling out your change.
⚠️ This PR contains breaking changes. Normally you should avoid that and make
your consumer backwards-compatible (meaning that updated consumers can still
accept old messages). There are a few exceptions:
If consumers already require these invariants in practice, and you're
just adjusting the JSON schema to reality, ignore this warning.
If you know what you are doing, this change could potentially be rolled out
to producers first, but that's not a flow we support.
versions in use:
The following repositories use one of the schemas you are editing. It is recommended to roll out schema changes in small PRs, meaning that if those used versions lag behind the latest, it is probably best to update those services before rolling out your change.
pip:sentry-kafka-schemas==0.1.90(upgrade)rust:sentry-kafka-schemas==0.1.90(upgrade)rust:sentry-kafka-schemas==0.1.86(upgrade)latest version: 0.1.102
changes considered breaking
**schemas/snuba-metrics-summaries.v1.schema.json** - ``` {"path": "", "change": {"RequiredAdd": {"property": "count"}}} ```⚠️ This PR contains breaking changes. Normally you should avoid that and make your consumer backwards-compatible (meaning that updated consumers can still accept old messages). There are a few exceptions:
If consumers already require these invariants in practice, and you're just adjusting the JSON schema to reality, ignore this warning.
If you know what you are doing, this change could potentially be rolled out to producers first, but that's not a flow we support.