Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref(crons): Remove volume_anomaly_result from mark_missing task #350

Conversation

evanpurkhiser
Copy link
Member

We'll no longer be using this, similar to GH-349.

See getsentry/sentry#80650

Copy link

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.

latest version: 0.1.118

There were changes to the JSON schema file, but we couldn't categorize any of
them. Therefore we don't know whether this change is safe to make.

This might be a gap in linting. Want to take a look at
https://github.com/getsentry/json-schema-diff/ and figure it out?

evanpurkhiser added a commit to getsentry/sentry that referenced this pull request Nov 13, 2024
We'll no longer be using this here. I will make a follow up PR to
`sentry-kafka-schemas` to remove the schema property
(getsentry/sentry-kafka-schemas#350)
@evanpurkhiser evanpurkhiser merged commit 7604f68 into main Nov 13, 2024
15 of 16 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/ref-crons-remove-volume-anomaly-result-from-mark-missing-task branch November 13, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants