Skip to content

Bump sentry-sdk[flask] from 1.43.0 to 2.5.1

Johannes Zumthurm requested to merge dependabot/pip/sentry-sdk-flask--2.5.1 into master

Created by: dependabot[bot]

Bumps sentry-sdk[flask] from 1.43.0 to 2.5.1.

Release notes

Sourced from sentry-sdk[flask]'s releases.

2.5.1

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

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

... (truncated)

Changelog

Sourced from sentry-sdk[flask]'s changelog.

2.5.1

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

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

... (truncated)

Commits
  • 411b1d4 Update CHANGELOG.md
  • d18ff4d release: 2.5.1
  • d818e8f Revert "Refactor the Celery Beat integration (#3105)" (#3144)
  • c2af1b0 feat(tracing): Warn if not-started transaction entered (#3003)
  • 7674bf2 test(scope): Ensure last_event_id cleared
  • dd15d32 fix(scope): Clear last_event_id on scope clear
  • 239cca2 Merge branch 'release/2.5.0'
  • 504e05e Update CHANGELOG.md
  • dbc02e6 release: 2.5.0
  • 9227968 feat(starlette): Allow to configure status codes to report to Sentry (#3008)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

Merge request reports