Bump sentry-sdk from 1.45.0 to 2.3.1 #12388
Closed
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-sdk from 1.45.0 to 2.3.1.
Release notes
Sourced from [sentry-sdk's releases](https://github.com/getsentry/sentry-python/releases).
... (truncated)
Changelog
Sourced from [sentry-sdk's changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md).
... (truncated)
Commits
a0ea6a9
Updated changelogf12712f
release: 2.3.135e9bab
Handle also byte arras as strings ([Bump snyk from 1.154.0 to 1.161.1 #3101](https://github.com/Handle also byte arrays keys getsentry/sentry-python#3101))45bf880
Do not crash exceptiongroup (by patching excepthook and keeping the name of t...0983f74
Merge branch 'release/2.3.0'4e74f91
Updated Changelogfadd277
Update CHANGELOG.md88dd524
release: 2.3.0121aa0e
Redis Cache Module - 1 - Prepare Code ([Bump boto3 from 1.9.134 to 1.9.137 #3073](https://github.com/Redis Cache Module - 1 - Prepare Code getsentry/sentry-python#3073))30f72a3
Django caching instrumentation update ([Clean up PNI colours #3009](https://github.com/Django caching instrumentation update getsentry/sentry-python#3009))Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)┆Issue is synchronized with this Jira Story