hypothesis / via

Proxies third-party PDF files and HTML pages with the Hypothesis client embedded, so you can annotate them
https://via.hypothes.is/
BSD 2-Clause "Simplified" License
20 stars 7 forks source link

Bump sentry-sdk from 2.13.0 to 2.17.0 #1448

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps sentry-sdk from 2.13.0 to 2.17.0.

Release notes

Sourced from sentry-sdk's releases.

2.17.0

Various fixes & improvements

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.

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.17.0

Various fixes & improvements

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

... (truncated)

Commits


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 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)