Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency sentry-sdk to v2 #268

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency sentry-sdk to v2 #268

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-sdk (changelog) ^1.14.0 -> ^2.0.0 age adoption passing confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.18.0

Compare Source

Various fixes & improvements

v2.17.0

Compare Source

Various fixes & improvements

v2.16.0

Compare Source

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

v2.15.0

Compare Source

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

v2.14.0

Compare Source

Various fixes & improvements

v2.13.0

Compare Source

Various fixes & improvements

  • New integration: Ray (#​2400) (#​2444) by @​glowskir

    Usage: (add the RayIntegration to your sentry_sdk.init() call and make sure it is called in the worker processes)

    import ray

import sentry_sdk
from sentry_sdk.integrations.ray import RayIntegration

def init_sentry():
    sentry_sdk.init(
        dsn="...",
        traces_sample_rate=1.0,
        integrations=[RayIntegration()],
    )

init_sentry()

ray.init(
    runtime_env=dict(worker_process_setup_hook=init_sentry), 
)

    For more information, see the documentation for the Ray integration.

  • New integration: Litestar (#​2413) (#​3358) by @​KellyWalker

    Usage: (add the LitestarIntegration to your sentry_sdk.init())

    from litestar import Litestar, get

import sentry_sdk
from sentry_sdk.integrations.litestar import LitestarIntegration

sentry_sdk.init(
    dsn="...",
    traces_sample_rate=1.0,
    integrations=[LitestarIntegration()],
)

@​get("/")
async def index() -> str:
    return "Hello, world!"

app = Litestar(...)

    For more information, see the documentation for the Litestar integration.

  • New integration: Dramatiq from @​jacobsvante (#​3397) by @​antonpirker
    Usage: (add the DramatiqIntegration to your sentry_sdk.init())

    import dramatiq

import sentry_sdk
from sentry_sdk.integrations.dramatiq import DramatiqIntegration

sentry_sdk.init(
    dsn="...",
    traces_sample_rate=1.0,
    integrations=[DramatiqIntegration()],
)

@​dramatiq.actor(max_retries=0)
def dummy_actor(x, y):
    return x / y

dummy_actor.send(12, 0)

    For more information, see the documentation for the Dramatiq integration.

  • New config option: Expose custom_repr function that precedes safe_repr invocation in serializer (#​3438) by @​sl0thentr0py

    See: https://docs.sentry.io/platforms/python/configuration/options/#custom-repr

  • Profiling: Add client SDK info to profile chunk (#​3386) by @​Zylphrex

  • Serialize vars early to avoid living references (#​3409) by @​sl0thentr0py

  • Deprecate hub-based sessions.py logic (#​3419) by @​szokeasaurusrex

  • Deprecate is_auto_session_tracking_enabled (#​3428) by @​szokeasaurusrex

  • Add note to generated yaml files (#​3423) by @​sentrivana

  • Slim down PR template (#​3382) by @​sentrivana

  • Use new banner in readme (#​3390) by @​sentrivana

v2.12.0

Compare Source

Various fixes & improvements

v2.11.0

Compare Source

Various fixes & improvements

  • Add disabled_integrations (#​3328) by @​sentrivana

    Disabling individual integrations is now much easier.
    Instead of disabling all automatically enabled integrations and specifying the ones
    you want to keep, you can now use the new
    disabled_integrations
    config option to provide a list of integrations to disable:

    import sentry_sdk
from sentry_sdk.integrations.flask import FlaskIntegration

sentry_sdk.init(

Do not use the Flask integration even if Flask is installed.

  disabled_integrations=[
      FlaskIntegration(),
  ],

)


- Use operation name as transaction name in Strawberry (#​3294) by @​sentrivana
- WSGI integrations respect `SCRIPT_NAME` env variable (#​2622) by @​sarvaSanjay
- Make Django DB spans have origin `auto.db.django` (#​3319) by @​antonpirker
- Sort breadcrumbs by time before sending (#​3307) by @​antonpirker
- Fix `KeyError('sentry-monitor-start-timestamp-s')` (#​3278) by @​Mohsen-Khodabakhshi
- Set MongoDB tags directly on span data (#​3290) by @​0Calories
- Lower logger level for some messages (#​3305) by @​sentrivana and @​antonpirker
- Emit deprecation warnings from `Hub` API (#​3280) by @​szokeasaurusrex
- Clarify that `instrumenter` is internal-only (#​3299) by @​szokeasaurusrex
- Support Django 5.1 (#​3207) by @​sentrivana
- Remove apparently unnecessary `if` (#​3298) by @​szokeasaurusrex
- Preliminary support for Python 3.13 (#​3200) by @​sentrivana
- Move `sentry_sdk.init` out of `hub.py` (#​3276) by @​szokeasaurusrex
- Unhardcode integration list (#​3240) by @​rominf
- Allow passing of PostgreSQL port in tests (#​3281) by @​rominf
- Add tests for `@ai_track` decorator (#​3325) by @​colin-sentry
- Do not include type checking code in coverage report (#​3327) by @​antonpirker
- Fix test_installed_modules (#​3309) by @​szokeasaurusrex
- Fix typos and grammar in a comment (#​3293) by @​szokeasaurusrex
- Fixed failed tests setup (#​3303) by @​antonpirker
- Only assert warnings we are interested in (#​3314) by @​szokeasaurusrex

v2.10.0

Compare Source

Various fixes & improvements

v2.9.0

Compare Source

Various fixes & improvements

v2.8.0

Compare Source

Various fixes & improvements

v2.7.1

Compare Source

Various fixes & improvements

v2.7.0

Compare Source

v2.6.0

Compare Source

v2.5.1

Compare Source

This change fixes a regression in our cron monitoring feature, which caused cron checkins not to be sent. The regression appears to have been introduced in version 2.4.0.

We recommend that all users, who use Cron monitoring and are currently running sentry-python ≥2.4.0, upgrade to this release as soon as possible!

Other fixes & improvements

v2.5.0

Compare Source

Various fixes & improvements

  • Allow to configure status codes to report to Sentry in Starlette and FastAPI (#​3008) by @​sentrivana

    By passing a new option to the FastAPI and Starlette integrations, you're now able to configure what
    status codes should be sent as events to Sentry. Here's how it works:

    from sentry_sdk.integrations.starlette import StarletteIntegration
from sentry_sdk.integrations.fastapi import FastApiIntegration

sentry_sdk.init(

...

  integrations=[
      StarletteIntegration(
          failed_request_status_codes=[403, range(500, 599)],
      ),
      FastApiIntegration(
          failed_request_status_codes=[403, range(500, 599)],
      ),
  ]

)


`failed_request_status_codes` expects a list of integers or containers (objects that allow membership checks via `in`)
of integers. Examples of valid `failed_request_status_codes`:

- `[500]` will only send events on HTTP 500.
- `[400, range(500, 599)]` will send events on HTTP 400 as well as the 500-599 range.
- `[500, 503]` will send events on HTTP 500 and 503.

The default is `[range(500, 599)]`.

See the [FastAPI](https://docs.sentry.io/platforms/python/integrations/fastapi/) and [Starlette](https://docs.sentry.io/platforms/python/integrations/starlette/) integration docs for more details.

- Support multiple keys with `cache_prefixes` (#​3136) by @​sentrivana
- Support integer Redis keys (#​3132) by @​sentrivana
- Update SDK version in CONTRIBUTING.md (#​3129) by @​sentrivana
- Bump actions/checkout from 4.1.4 to 4.1.5 (#​3067) by @​dependabot

v2.4.0

Compare Source

Various fixes & improvements

v2.3.1

Compare Source

Various fixes & improvements

v2.3.0

Compare Source

Various fixes & improvements

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 25, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 919b628 to d5d5528 Compare August 5, 2024 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants