Skip to content

Releases: getsentry/sentry-python

1.30.0

29 Aug 13:46

Choose a tag to compare

Various fixes & improvements

  • Officially support Python 3.11 (#2300) by @sentrivana

  • Context manager monitor (#2290) by @szokeasaurusrex

  • Set response status code in transaction response context. (#2312) by @antonpirker

  • Add missing context kwarg to _sentry_task_factory (#2267) by @JohnnyDeuss

  • In Postgres take the connection params from the connection (#2308) by @antonpirker

  • Experimental: Allow using OTel for performance instrumentation (#2272) by @sentrivana

    This release includes experimental support for replacing Sentry's default
    performance monitoring solution with one powered by OpenTelemetry without having
    to do any manual setup.

    Try it out by installing pip install sentry-sdk[opentelemetry-experimental] and
    then initializing the SDK with:

    sentry_sdk.init(
        # ...your usual options...
        _experiments={"otel_powered_performance": True},
    )

    This enables OpenTelemetry performance monitoring support for some of the most
    popular frameworks and libraries (Flask, Django, FastAPI, requests...).

    We're looking forward to your feedback! Please let us know about your experience
    in this discussion: getsentry/sentry#55023

    Important note: Please note that this feature is experimental and in a
    proof-of-concept stage and is not meant for production use. It may be changed or
    removed at any point.

  • Enable backpressure handling by default (#2298) by @sl0thentr0py

    The SDK now dynamically downsamples transactions to reduce backpressure in high
    throughput systems. It starts a new Monitor thread to perform some health checks
    which decide to downsample (halved each time) in 10 second intervals till the system
    is healthy again.

    To disable this behavior, use:

    sentry_sdk.init(
        # ...your usual options...
        enable_backpressure_handling=False,
    )

    If your system serves heavy load, please let us know how this feature works for you!
    Check out the documentation for more information.

  • Stop recording spans for internal web requests to Sentry (#2297) by @szokeasaurusrex

  • Add test for ThreadPoolExecutor (#2259) by @gggritso

  • Add docstrings for Scope.update_from_* (#2311) by @sentrivana

  • Moved is_sentry_url to utils (#2304) by @szokeasaurusrex

  • Fix: arq attribute error on settings, support worker args (#2260) by @rossmacarthur

  • Fix: Exceptions include detail property for their value (#2193) by @nicolassanmar

  • build(deps): bump mypy from 1.4.1 to 1.5.1 (#2319) by @dependabot

  • build(deps): bump sphinx from 7.1.2 to 7.2.4 (#2322) by @dependabot

  • build(deps): bump sphinx from 7.0.1 to 7.1.2 (#2296) by @dependabot

  • build(deps): bump checkouts/data-schemas from 1b85152 to ebc77d3 (#2254) by @dependabot

1.29.2

01 Aug 14:40

Choose a tag to compare

Various fixes & improvements

1.29.1

01 Aug 11:31

Choose a tag to compare

Various fixes & improvements

1.29.0

31 Jul 09:27

Choose a tag to compare

Various fixes & improvements

1.28.1

13 Jul 10:14
e1c77cc

Choose a tag to compare

Various fixes & improvements

1.28.0

10 Jul 10:39
069d390

Choose a tag to compare

Various fixes & improvements

1.27.1

06 Jul 13:03
40906dc

Choose a tag to compare

Various fixes & improvements

  • Add Starlette/FastAPI template tag for adding Sentry tracing information (#2225) by @antonpirker
    • By adding {{ sentry_trace_meta }} to your Starlette/FastAPI Jinja2 templates we will include Sentry trace information as a meta tag in the rendered HTML to allow your frontend to pick up and continue the trace started in the backend.
  • Fixed generation of baggage when a DSC is already in propagation context (#2232) by @antonpirker
  • Handle explicitly passing None for trace_configs in aiohttp (#2230) by @Harmon758
  • Support newest Starlette versions (#2227) by @antonpirker

1.27.0

04 Jul 12:30
7ba4fd9

Choose a tag to compare

Various fixes & improvements

1.26.0

22 Jun 11:14
892f794

Choose a tag to compare

Various fixes & improvements

1.25.1

07 Jun 15:54

Choose a tag to compare

Django update (ongoing)

Collections of improvements to our Django integration.

By: @mgaligniana (#1773)

Various fixes & improvements

  • Fix parse_url (#2161) by @sentrivana and @antonpirker

    Our URL sanitization used in multiple integrations broke with the recent Python security update. If you started seeing ValueErrors with "'Filtered' does not appear to be an IPv4 or IPv6 address", this release fixes that. See the original issue for more context.

  • Better version parsing in integrations (#2152) by @antonpirker

    We now properly support all integration versions that conform to PEP 440. This replaces our naΓ―ve version parsing that wouldn't accept versions such as 2.0.0rc1 or 2.0.5.post1.

  • Align HTTP status code as span data field http.response.status_code (#2113) by @antonpirker

  • Do not encode cached value to determine size (#2143) by @sentrivana

  • Fix using unittest.mock whenever available (#1926) by @mgorny

  • Fix 2.7 common tests (#2145) by @sentrivana

  • Bump actions/stale from 6 to 8 (#1978) by @dependabot

  • Bump black from 22.12.0 to 23.3.0 (#1984) by @dependabot

  • Bump mypy from 1.2.0 to 1.3.0 (#2110) by @dependabot

  • Bump sphinx from 5.3.0 to 7.0.1 (#2112) by @dependabot