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.19.2 - autoclosed #280

Closed
wants to merge 1 commit into from
Closed

fix(deps): update dependency sentry-sdk to v2.19.2 - autoclosed #280

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-sdk (changelog) 2.14.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

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 changed the title fix(deps): update dependency sentry-sdk to v2.15.0 fix(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 056a118 to 4d39d76 Compare October 8, 2024 13:44
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.16.0 fix(deps): update dependency sentry-sdk to v2.17.0 Oct 17, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 4d39d76 to ef47cb1 Compare October 17, 2024 10:53
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from ef47cb1 to cba5535 Compare November 4, 2024 14:55
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.17.0 fix(deps): update dependency sentry-sdk to v2.18.0 Nov 4, 2024
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.18.0 fix(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 cba5535 to ba16cd9 Compare November 21, 2024 16:26
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from ba16cd9 to 4926462 Compare December 5, 2024 16:36
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.0 fix(deps): update dependency sentry-sdk to v2.19.1 Dec 5, 2024
@renovate
fix(deps): update dependency sentry-sdk to v2.19.2
72ed72f 
| datasource | package    | from   | to     |
| ---------- | ---------- | ------ | ------ |
| pypi       | sentry-sdk | 2.14.0 | 2.19.2 |
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 4926462 to 72ed72f Compare December 6, 2024 09:23
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.1 fix(deps): update dependency sentry-sdk to v2.19.2 Dec 6, 2024
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.2 fix(deps): update dependency sentry-sdk to v2.19.2 - autoclosed Dec 21, 2024
@renovate renovate bot closed this Dec 21, 2024
@renovate renovate bot deleted the renovate/sentry-sdk-2.x branch December 21, 2024 15:23
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.2 - autoclosed fix(deps): update dependency sentry-sdk to v2.19.2 Dec 21, 2024
@renovate renovate bot reopened this Dec 21, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from a062862 to 72ed72f Compare December 21, 2024 15:33
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.2 fix(deps): update dependency sentry-sdk to v2.19.2 - autoclosed Dec 21, 2024
@renovate renovate bot closed this Dec 21, 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
None yet
Projects
Infrastructure
Status: Done
Milestone
No milestone
Development

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