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.

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

chore(deps): update dependency sentry-sdk to v2.10.0 - autoclosed #57

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 4, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

getsentry/sentry-python (sentry-sdk)

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

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.4.0 chore(deps): update dependency sentry-sdk to v2.5.0 Jun 6, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from c95fc6a to 7eb25fa Compare June 6, 2024 12:56
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.5.0 chore(deps): update dependency sentry-sdk to v2.5.1 Jun 7, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 7eb25fa to 19dd52c Compare June 7, 2024 21:55
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 19dd52c to 70d6e86 Compare June 19, 2024 15:59
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.5.1 chore(deps): update dependency sentry-sdk to v2.6.0 Jun 19, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 70d6e86 to 7e859d2 Compare June 26, 2024 12:18
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.6.0 chore(deps): update dependency sentry-sdk to v2.7.0 Jun 26, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 7e859d2 to 76d5f8b Compare June 27, 2024 16:20
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.7.0 chore(deps): update dependency sentry-sdk to v2.7.1 Jun 27, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 76d5f8b to 2494631 Compare July 8, 2024 11:20
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.7.1 chore(deps): update dependency sentry-sdk to v2.8.0 Jul 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.8.0 chore(deps): update dependency sentry-sdk to v2.9.0 Jul 10, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 2494631 to c97cb85 Compare July 10, 2024 10:50
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from c97cb85 to 3da9462 Compare July 15, 2024 11:49
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.9.0 chore(deps): update dependency sentry-sdk to v2.10.0 Jul 15, 2024
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.10.0 chore(deps): update dependency sentry-sdk to v2.10.0 - autoclosed Jul 18, 2024
@renovate renovate bot closed this Jul 18, 2024
@renovate renovate bot deleted the renovate/sentry-sdk-2.x branch July 18, 2024 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants