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

chore(deps): update dependency sentry-sdk to v2.19.2 #711

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

chore(deps): update dependency sentry-sdk to v2.19.2 #711

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 13, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-sdk (changelog) ==2.12.0 -> ==2.19.2 age adoption passing confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.19.2

Compare Source

Various fixes & improvements

v2.19.1

Compare Source

Various fixes & improvements

v2.19.0

Compare Source

Various fixes & improvements

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

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 renovate label Aug 13, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from e4e1f23 to 3cf8878 Compare September 9, 2024 15:42
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.13.0 chore(deps): update dependency sentry-sdk to v2.14.0 Sep 9, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 3cf8878 to a0a28f0 Compare October 1, 2024 16:09
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.14.0 chore(deps): update dependency sentry-sdk to v2.15.0 Oct 1, 2024
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.15.0 chore(deps): update dependency sentry-sdk to v2.16.0 Oct 8, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from a0a28f0 to 6ea0fab Compare October 8, 2024 15:52
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 6ea0fab to 5f5d763 Compare October 17, 2024 11:46
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.16.0 chore(deps): update dependency sentry-sdk to v2.17.0 Oct 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.17.0 chore(deps): update dependency sentry-sdk to v2.18.0 Nov 4, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 5f5d763 to fb690e5 Compare November 4, 2024 16:13
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from fb690e5 to 4261e4b Compare November 21, 2024 17:03
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.18.0 chore(deps): update dependency sentry-sdk to v2.19.0 Nov 21, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 4261e4b to 481e5cb Compare December 5, 2024 16:52
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.19.0 chore(deps): update dependency sentry-sdk to v2.19.1 Dec 5, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 481e5cb to ae1e640 Compare December 6, 2024 11:59
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.19.1 chore(deps): update dependency sentry-sdk to v2.19.2 Dec 6, 2024
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
renovate
Projects
None yet
Milestone
No milestone
Development

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