build(deps): bump sentry-sdk from 2.14.0 to 2.15.0

[dependabot]

Bumps sentry-sdk from 2.14.0 to 2.15.0.

Release notes

Sourced from sentry-sdk's releases.

2.15.0

Integrations

• Configure HTTP methods to capture in ASGI/WSGI middleware and frameworks (#3531) by @​antonpirker

  We've added a new option to the Django, Flask, Starlette and FastAPI integrations called http_methods_to_capture. 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 (substitute Flask for your framework integration):

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

• Django: Allow ASGI to use drf_request in DjangoRequestExtractor (#3572) by @​PakawiNz

• Django: Don't let RawPostDataException bubble up (#3553) by @​sentrivana

• Django: Add sync_capable to SentryWrappingMiddleware (#3510) by @​szokeasaurusrex

• AIOHTTP: Add failed_request_status_codes (#3551) 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=[
          AioHttpIntegration(
              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.

• AIOHTTP: Delete test which depends on AIOHTTP behavior (#3568) by @​szokeasaurusrex

• AIOHTTP: Handle invalid responses (#3554) by @​szokeasaurusrex

• FastAPI/Starlette: Support new failed_request_status_codes (#3563) by @​szokeasaurusrex

  The format of failed_request_status_codes has changed from a list

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.15.0

Integrations

• Configure HTTP methods to capture in ASGI/WSGI middleware and frameworks (#3531) by @​antonpirker

  We've added a new option to the Django, Flask, Starlette and FastAPI integrations called http_methods_to_capture. 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 (substitute Flask for your framework integration):

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

• Django: Allow ASGI to use drf_request in DjangoRequestExtractor (#3572) by @​PakawiNz

• Django: Don't let RawPostDataException bubble up (#3553) by @​sentrivana

• Django: Add sync_capable to SentryWrappingMiddleware (#3510) by @​szokeasaurusrex

• AIOHTTP: Add failed_request_status_codes (#3551) 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=[
          AioHttpIntegration(
              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.

• AIOHTTP: Delete test which depends on AIOHTTP behavior (#3568) by @​szokeasaurusrex

• AIOHTTP: Handle invalid responses (#3554) by @​szokeasaurusrex

• FastAPI/Starlette: Support new failed_request_status_codes (#3563) by @​szokeasaurusrex

... (truncated)

Commits

• 65909ed Update CHANGELOG.md
• 97b6d9f Fix changelog
• 5de346c Refactor changelog
• 7bee75f release: 2.15.0
• 1c64ff7 Configure HTTP methods to capture in WSGI middleware and frameworks (#3531)
• a3ab1ea XFail one of the Lambda tests (#3592)
• 05411ff allowing ASGI to use drf_request in DjangoRequestExtractor (#3572)
• 4636afc fix(tracing): Fix add_query_source with modules outside of project root (#3...
• aed18d4 build(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#3585)
• 205591e Test more integrations on 3.13 (#3578)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

[relud]

@dependabot rebase