Bump sentry-sdk[flask] from 1.43.0 to 1.45.0

Created by: dependabot[bot]

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

Release notes

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

1.45.0

This is the final 1.x release for the forseeable future. Development will continue on the 2.x release line. The first 2.x version will be available in the next few weeks.

Various fixes & improvements

• Allow to upsert monitors (#2929) by @​sentrivana

  It's now possible to provide monitor_config to the monitor decorator/context manager directly:

  from sentry_sdk.crons import monitor
  All keys except schedule are optional
  monitor_config = {
  "schedule": {"type": "crontab", "value": "0 0 * * *"},
  "timezone": "Europe/Vienna",
  "checkin_margin": 10,
  "max_runtime": 10,
  "failure_issue_threshold": 5,
  "recovery_threshold": 5,
  }
  @​monitor(monitor_slug='<monitor-slug>', monitor_config=monitor_config)
  def tell_the_world():
  print('My scheduled task...')

  Check out the cron docs for details.

• Add Django signals_denylist to filter signals that are attached to by signals_spans (#2758) by @​lieryan

  If you want to exclude some Django signals from performance tracking, you can use the new signals_denylist Django option:

  import django.db.models.signals
  import sentry_sdk
  sentry_sdk.init(
  ...
  integrations=[
  DjangoIntegration(
  ...
  signals_denylist=[
  django.db.models.signals.pre_init,
  django.db.models.signals.post_init,
  ],
  ),
  ],
  )

... (truncated)

Changelog

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

1.45.0

This is the final 1.x release for the forseeable future. Development will continue on the 2.x release line. The first 2.x version will be available in the next few weeks.

Various fixes & improvements

• Allow to upsert monitors (#2929) by @​sentrivana

  It's now possible to provide monitor_config to the monitor decorator/context manager directly:

  from sentry_sdk.crons import monitor
  All keys except schedule are optional
  monitor_config = {
  "schedule": {"type": "crontab", "value": "0 0 * * *"},
  "timezone": "Europe/Vienna",
  "checkin_margin": 10,
  "max_runtime": 10,
  "failure_issue_threshold": 5,
  "recovery_threshold": 5,
  }
  @​monitor(monitor_slug='<monitor-slug>', monitor_config=monitor_config)
  def tell_the_world():
  print('My scheduled task...')

  Check out the cron docs for details.

• Add Django signals_denylist to filter signals that are attached to by signals_spans (#2758) by @​lieryan

  If you want to exclude some Django signals from performance tracking, you can use the new signals_denylist Django option:

  import django.db.models.signals
  import sentry_sdk
  sentry_sdk.init(
  ...
  integrations=[
  DjangoIntegration(
  ...
  signals_denylist=[
  django.db.models.signals.pre_init,
  django.db.models.signals.post_init,
  ],
  ),
  ],
  )

... (truncated)

Commits

• 51a906c Update CHANGELOG.md
• 7570e39 release: 1.45.0
• e22abb6 fix(metrics): Change data_category from statsd to metric_bucket (#2954)
• fab65e6 feat(metrics): New normalization of keys, values, units (#2946)
• a584653 feat(typing): Make monitor_config a TypedDict (#2931)
• a1ab339 feat(metrics): Add value, unit to before_emit_metric (#2958)
• 18ccb8f chore: Remove experimental metric summary options (#2957)
• a422dd7 fix(profiler): Accessing mro might throw a ValueError (#2952)
• 11e1f9a feat(integrations): Add django signals_denylist to filter signals that are at...
• f5ec34c build(deps): bump types-protobuf from 4.24.0.20240311 to 4.24.0.20240408 (#2941)
• Additional commits viewable in compare view

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)