Skip to content

3.0.0

Latest

Choose a tag to compare

@sentry-release-bot sentry-release-bot released this 30 Oct 08:59

Breaking Changes 🛠

Git

  • Raise GitGrantKeyError for a missing or unusable git grant key, so callers can tell their own misconfiguration apart from a bad grant by @vaind in #171
    • It's a ValueError, not an SCMCodedError. A public key that isn't a string used to raise TypeError.
    • verify_grant([], token) raises it. 2.x refused the grant with GitInvalidGrant (a 403 from GitServer).
  • Add require_private_key to check a signing key at startup, and generate_private_key to make one for tests by @vaind in #171
  • Answer a remote that isn't https, a refused remote host and an untrusted TLS certificate with a 500 instead of a 502, since no retry can fix them by @vaind in #171
  • Document that get_token may raise a coded error, which GitServer answers by its code, e.g. ResourceServiceUnavailable as a 503 by @vaind in #171
  • Upgrade notes for earlier 3.0.0 changes by @vaind in #171
    • GitServer's get_token must return an scm.Secret, or every relayed request fails with TypeError (#167).
    • Once Sentry maps RestrictedIPAddress to GitRemoteRefused with GitRelay(map_error=...), its refusal of internal addresses changes from a 503 to a 500 (#168).
  • Sign git grants with Ed25519 by @vaind in #170

New Features ✨

  • (git) Let callers map adapter errors to coded errors, like a refused host by @vaind in #168

Bug Fixes 🐛

  • (git) Keep the provider token out of error reports by @vaind in #167
  • (rpc) Keep request signatures out of error reports by @vaind in #169

Documentation 📚

  • (release) Describe the auto-versioned release flow by @vaind in #166