ref(releases): dont send back release stats on update #77832
Merged
+24
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I can't think of a reason why release stats are super necessary on updates to a release. This causes extra load on snuba, and can also result in release update failures when snuba is being rate limited or 429ing.
If this is too aggressive, we could consider catching 429's in the release serializer and making them empty instead.
releasing under an option so we can rollback if any problems are observed.