Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump sentry-sdk from 2.18.0 to 2.19.2 #13247

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 9, 2024

Bumps sentry-sdk from 2.18.0 to 2.19.2.

Release notes

Sourced from sentry-sdk's releases.

2.19.2

Various fixes & improvements

2.19.1

Various fixes & improvements

2.19.0

Various fixes & improvements

Changelog

Sourced from sentry-sdk's changelog.

2.19.2

Various fixes & improvements

2.19.1

Various fixes & improvements

2.19.0

Various fixes & improvements

Commits
  • 163762f release: 2.19.2
  • 8f9461e Deepcopy and ensure get_all function always terminates (#3861)
  • fd56608 Merge branch 'release/2.19.1'
  • 7ab7fe6 Cleanup chalice test environment (#3858)
  • 231a6a1 Update CHANGELOG.md
  • c591b64 release: 2.19.1
  • 7a6d460 Copy scope.client reference as well (#3857)
  • 5a09770 fix(spotlight): Don't give up on Spotlight on 3 errors (#3856)
  • 31fdcfa fix(django): Fix errors when instrumenting Django cache (#3855)
  • 5891717 Script for checking if our instrumented libs are python 3.13 compatible (#3425)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 2.18.0 to 2.19.2.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@2.18.0...2.19.2)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added backend dependencies Pull requests that update a dependency file engineering pip Used for dependabot PR's having to do with pip/python labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend dependencies Pull requests that update a dependency file engineering pip Used for dependabot PR's having to do with pip/python
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants