Repository navigation
ref: bump sentry-scm to 3.0.0 - #129290
Merged
Merged
Conversation
Refs CW-2222
github-actions
Bot
added
the
Scope: Backend
vaind
approved these changes
Oct 30, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps
sentry-scmfrom 2.0.0 to 3.0.0. The lockfile also picks upcryptographyas a direct dependency of sentry-scm; the lockedcryptography(50.0.0) andpyjwt(2.15.0) already meet 3.0.0's new floors (>=48.0.1,>=2.14.0).No code changes are needed on master. The 3.0.0 breaking changes are all in
scm.git(Ed25519 grants,GitServer(public_keys=...),get_tokenreturning anscm.Secret,GitRelay(map_error=...),GitGrantKeyError, and the 502 → 500 status changes), and nothing on master usesscm.gityet. The only user is the git endpoint in #128444, which is already written against 3.0.0 and only needs this bump to pass CI. The one other change that touches master's code, getsentry/scm-platform#169, is backward compatible forRpcServer's callers.Landing this first lets #128444 drop its "bump sentry-scm" checklist item after a rebase. If you'd rather keep the bump inside #128444, close this one.
This PR needs no deploy config or secrets.
SCM_GIT_GRANT_PUBLIC_KEYS(Ed25519 public keys as PEM, matching Seer's signing key) comes in with #128444.Upstream: getsentry/scm-platform#168, getsentry/scm-platform#170, getsentry/scm-platform#171
Refs CW-2222
via Ivan Dlugos.
--
View Session [Sentry]