Bump sentry-sdk from 2.1.1 to 2.16.0

[dependabot]

Bumps sentry-sdk from 2.1.1 to 2.16.0.

Release notes

Sourced from sentry-sdk's releases.

2.16.0

Integrations

• Bottle: Add failed_request_status_codes (#3618) by @​szokeasaurusrex

  You can now define a set of integers that will determine which status codes should be reported to Sentry.

  sentry_sdk.init(
      integrations=[
          BottleIntegration(
              failed_request_status_codes={403, *range(500, 600)},
          )
      ]
  )

  Examples of valid failed_request_status_codes:

  • {500} will only send events on HTTP 500.
  • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
  • {500, 503} will send events on HTTP 500 and 503.
  • set() (the empty set) will not send events for any HTTP status code.

  The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

• Bottle: Delete never-reached code (#3605) by @​szokeasaurusrex

• Redis: Remove flaky test (#3626) by @​sentrivana

• Django: Improve getting psycopg3 connection info (#3580) by @​nijel

• Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @​BYK

• Django: Open relevant error when SpotlightMiddleware is on (#3614) by @​BYK

• Django: Support http_methods_to_capture in ASGI Django (#3607) by @​sentrivana

  ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

  Here's how to use it:

  sentry_sdk.init(
      integrations=[
          DjangoIntegration(
              http_methods_to_capture=("GET", "POST"),
          ),
      ],
  )

Miscellaneous

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.16.0

Integrations

• Bottle: Add failed_request_status_codes (#3618) by @​szokeasaurusrex

  You can now define a set of integers that will determine which status codes should be reported to Sentry.

  sentry_sdk.init(
      integrations=[
          BottleIntegration(
              failed_request_status_codes={403, *range(500, 600)},
          )
      ]
  )

  Examples of valid failed_request_status_codes:

  • {500} will only send events on HTTP 500.
  • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
  • {500, 503} will send events on HTTP 500 and 503.
  • set() (the empty set) will not send events for any HTTP status code.

  The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

• Bottle: Delete never-reached code (#3605) by @​szokeasaurusrex

• Redis: Remove flaky test (#3626) by @​sentrivana

• Django: Improve getting psycopg3 connection info (#3580) by @​nijel

• Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @​BYK

• Django: Open relevant error when SpotlightMiddleware is on (#3614) by @​BYK

• Django: Support http_methods_to_capture in ASGI Django (#3607) by @​sentrivana

  ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

  Here's how to use it:

  sentry_sdk.init(
      integrations=[
          DjangoIntegration(
              http_methods_to_capture=("GET", "POST"),
          ),
      ],
  )

Miscellaneous

... (truncated)

Commits

• 9098601 Fix changelog formatting
• b731910 Update CHANGELOG.md
• 0df20a7 release: 2.16.0
• 01b4687 Remove flaky test (#3626)
• 3945fc1 Add 3.13 to setup.py (#3574)
• c110ff3 Add 3.13 to basepython (#3589)
• d0eca65 feat(bottle): Add failed_request_status_codes (#3618)
• d34c99a feat: Add opportunistic Brotli compression (#3612)
• 4f79aec fix(django): improve getting psycopg3 connection info (#3580)
• 2d2e548 feat: Add __notes__ support (#3620)
• Additional commits viewable in compare view

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)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Test Results

1 tests  ±0   1 ✅ ±0   0s ⏱️ ±0s
1 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit e5b4a4f. ± Comparison against base commit e1da7e9.

[dependabot]

Superseded by #115.