Skip to content

Releases: getsentry/sentry-python

2.22.0

17 Feb 14:12
@getsentry-bot getsentry-bot
2.22.0
1fcd364
This commit was signed with the committer’s verified signature. The key has expired.
antonpirker Anton Pirker
GPG key ID: 0B0ECD22213A8A01
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.22.0 Latest
Latest

Various fixes & improvements

Contributors

cmanallen, Zylphrex, and 2 other contributors
Assets 6
Loading

2.21.0

12 Feb 10:21
@getsentry-bot getsentry-bot
2.21.0
dc1460a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.21.0

Various fixes & improvements

Contributors

antonpirker, constantinius, and 10 other contributors
Assets 6
Loading

2.20.0

14 Jan 09:51
@getsentry-bot getsentry-bot
2.20.0
4e0505e
This commit was signed with the committer’s verified signature. The key has expired.
antonpirker Anton Pirker
GPG key ID: 0B0ECD22213A8A01
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.20.0

Contributors

antonpirker, patrick91, and 7 other contributors
Assets 6
Loading

2.19.2

06 Dec 08:23
@getsentry-bot getsentry-bot
2.19.2
163762f
Compare
Choose a tag to compare
2.19.2

Various fixes & improvements

Contributors

antonpirker and cmanallen
Assets 6
Loading

2.19.1

05 Dec 15:18
@getsentry-bot getsentry-bot
2.19.1
231a6a1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.19.1

Various fixes & improvements

Contributors

BYK, antonpirker, and 5 other contributors
Assets 6
Loading

2.19.0

21 Nov 15:42
@getsentry-bot getsentry-bot
2.19.0
039c220
This commit was signed with the committer’s verified signature. The key has expired.
antonpirker Anton Pirker
GPG key ID: 0B0ECD22213A8A01
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.19.0

Various fixes & improvements

Contributors

BYK, antonpirker, and 9 other contributors
Assets 6
Loading

2.18.0

04 Nov 13:58
@getsentry-bot getsentry-bot
2.18.0
09946cb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.18.0

Various fixes & improvements

Contributors

BYK, cmanallen, and 6 other contributors
Assets 6
Loading

2.17.0

17 Oct 08:48
@getsentry-bot getsentry-bot
2.17.0
e44c9ee
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.17.0

Various fixes & improvements

Contributors

BYK, rbasoalto, and 5 other contributors
Assets 6
Loading

2.16.0

08 Oct 12:39
@getsentry-bot getsentry-bot
2.16.0
9098601
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
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

Contributors

BYK, antonpirker, and 4 other contributors
Assets 6
Loading

2.15.0

01 Oct 14:12
@getsentry-bot getsentry-bot
2.15.0
65909ed
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
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
    of integers and containers to a set:

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

    The old way of defining failed_request_status_codes will continue to work
    for the time being. Examples of valid new-style 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.

  • FastAPI/Starlette: Fix failed_request_status_codes=[] (#3561) by @szokeasaurusrex

  • FastAPI/Starlette: Remove invalid failed_request_status_code tests (#3560) by @szokeasaurusrex

  • FastAPI/Starlette: Refactor shared test parametrization (#3562) by @szokeasaurusrex

Miscellaneous

Contributors

BYK, antonpirker, and 6 other contributors
Assets 6
Loading