chore(deps): bump sentry-sdk from 2.3.1 to 2.5.0

[dependabot]

Bumps sentry-sdk from 2.3.1 to 2.5.0.

Release notes

Sourced from sentry-sdk's releases.

2.5.0

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 and 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

2.4.0

Various fixes & improvements

• Celery: Made cache.key span data field a list (#3110) by @​antonpirker
• Celery Beat: Refactor the Celery Beat integration (#3105) by @​antonpirker
• GRPC: Add None check for grpc.aio interceptor (#3109) by @​ordinary-jamie
• Docs: Remove last_event_id from migration guide (#3126) by @​szokeasaurusrex
• fix(django): Proper transaction names for i18n routes (#3104) by @​sentrivana
• fix(scope): Copy _last_event_id in Scope.__copy__ (#3123) by @​szokeasaurusrex

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.5.0

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 and 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

2.4.0

Various fixes & improvements

• Celery: Made cache.key span data field a list (#3110) by @​antonpirker
• Celery Beat: Refactor the Celery Beat integration (#3105) by @​antonpirker
• GRPC: Add None check for grpc.aio interceptor (#3109) by @​ordinary-jamie
• Docs: Remove last_event_id from migration guide (#3126) by @​szokeasaurusrex

... (truncated)

Commits

• 504e05e Update CHANGELOG.md
• dbc02e6 release: 2.5.0
• 9227968 feat(starlette): Allow to configure status codes to report to Sentry (#3008)
• ac4d657 fix(redis): Support multiple keys with cache_prefixes (#3136)
• 8f80dfe fix(cache): Fix key_as_string (#3132)
• c2c7896 build(deps): bump actions/checkout from 4.1.4 to 4.1.5 (#3067)
• 6f87c0d Update SDK version in CONTRIBUTING.md (#3129)
• 572916b Merge branch 'release/2.4.0'
• 505a491 Updated changelog
• 4520359 release: 2.4.0
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.