Skip to content

Commit

Permalink
Bump sentry-sdk from 2.2.0 to 2.5.1
Browse files Browse the repository at this point in the history
Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 2.2.0 to 2.5.1.
- [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.2.0...2.5.1)

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

Signed-off-by: dependabot[bot] <support@github.com>
  • Loading branch information
dependabot[bot] committed Jun 17, 2024
1 parent a9e3de5 commit 82b6176
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion requirements-dev.txt
Original file line number Diff line number Diff line change
Expand Up @@ -738,7 +738,7 @@ sarif-om==1.0.4
# cfn-lint
secretstorage==3.3.3
# via keyring
sentry-sdk==2.2.0
sentry-sdk==2.5.1
# via -r requirements-tests.txt
six==1.16.0
# via
Expand Down
2 changes: 1 addition & 1 deletion requirements-docs.txt
Original file line number Diff line number Diff line change
Expand Up @@ -750,7 +750,7 @@ sarif-om==1.0.4
# via
# -r requirements-tests.txt
# cfn-lint
sentry-sdk==2.2.0
sentry-sdk==2.5.1
# via
# -r requirements-docs.in
# -r requirements-tests.txt
Expand Down
2 changes: 1 addition & 1 deletion requirements-tests.txt
Original file line number Diff line number Diff line change
Expand Up @@ -602,7 +602,7 @@ s3transfer==0.10.1
# boto3
sarif-om==1.0.4
# via cfn-lint
sentry-sdk==2.2.0
sentry-sdk==2.5.1
# via -r requirements.txt
six==1.16.0
# via
Expand Down
2 changes: 1 addition & 1 deletion requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -324,7 +324,7 @@ rsa==4.9
# via google-auth
s3transfer==0.10.1
# via boto3
sentry-sdk==2.2.0
sentry-sdk==2.5.1
# via -r requirements.in
six==1.16.0
# via
Expand Down

0 comments on commit 82b6176

Please sign in to comment.