feat: Use semantic versioning for Sentry releases #28638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of using the commit SHA for our Sentry releases, use a more semantic version: CalVer+<build SHA> This also splits up the backend/frontend Sentry releases where previously they were in the same release (which implies they are always deployed together). This will be needed for independent frontend deploys.
evanpurkhiser
approved these changes
Sep 16, 2021
joshuarli
reviewed
Sep 16, 2021
joshuarli
approved these changes
Sep 17, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Instead of using the commit SHA for our Sentry releases, use a more semantic version: CalVer+
This also splits up the backend/frontend Sentry releases where previously they were in the same release (which implies they are always deployed together). This will be needed for independent frontend deploys.