Bump sentry-sdk[flask] from 2.20.0 to 2.25.1

[dependabot]

Bumps sentry-sdk[flask] from 2.20.0 to 2.25.1.

Release notes

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

2.25.1

Various fixes & improvements

• fix(logs): Add a class which batches groups of logs together. (#4229) by @​colin-sentry
• fix(logs): Use repr instead of json for message and arguments (#4227) by @​colin-sentry
• fix(logs): Debug output from Sentry logs should always be debug level. (#4224) by @​antonpirker
• fix(ai): Do not consume anthropic streaming stop (#4232) by @​colin-sentry
• fix(spotlight): Do not spam sentry_sdk.warnings logger w/ Spotlight (#4219) by @​BYK
• fix(docs): fixed code snippet (#4218) by @​antonpirker
• build(deps): bump actions/create-github-app-token from 1.11.7 to 1.12.0 (#4214) by @​dependabot

2.25.0

Various fixes & improvements

• New Beta Feature Enable Sentry logs in logging Integration (#4143) by @​colin-sentry

  You can now send existing log messages to the new Sentry Logs feature.

  For more information see: Logs in Sentry 🚀 getsentry/sentry#86804

  This is how you can use it (Sentry Logs is in beta right now so the API can still change):

  import logging
  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  Setup Sentry SDK to send log messages with a level of "error" or higher to Sentry.
  sentry_sdk.init(
  dsn="...",
  _experiments={
  "enable_sentry_logs": True
  }
  integrations=[
  LoggingIntegration(sentry_logs_level=logging.ERROR),
  ]
  )
  Your existing logging setup
  some_logger = logging.Logger("some-logger")
  some_logger.info('In this example info events will not be sent to Sentry logs. my_value=%s', my_value)
  some_logger.error('But error events will be sent to Sentry logs. my_value=%s', my_value)

• Spotlight: Sample everything 100% w/ Spotlight & no DSN set (#4207) by @​BYK

• Dramatiq: use set_transaction_name (#4175) by @​timdrijvers

• toxgen: Make it clearer which suites can be migrated (#4196) by @​sentrivana

• Move Litestar under toxgen (#4197) by @​sentrivana

... (truncated)

Changelog

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

2.25.1

Various fixes & improvements

• fix(logs): Add a class which batches groups of logs together. (#4229) by @​colin-sentry
• fix(logs): Use repr instead of json for message and arguments (#4227) by @​colin-sentry
• fix(logs): Debug output from Sentry logs should always be debug level. (#4224) by @​antonpirker
• fix(ai): Do not consume anthropic streaming stop (#4232) by @​colin-sentry
• fix(spotlight): Do not spam sentry_sdk.warnings logger w/ Spotlight (#4219) by @​BYK
• fix(docs): fixed code snippet (#4218) by @​antonpirker
• build(deps): bump actions/create-github-app-token from 1.11.7 to 1.12.0 (#4214) by @​dependabot

2.25.0

Various fixes & improvements

• New Beta Feature Enable Sentry logs in logging Integration (#4143) by @​colin-sentry

  You can now send existing log messages to the new Sentry Logs feature.

  For more information see: Logs in Sentry 🚀 getsentry/sentry#86804

  This is how you can use it (Sentry Logs is in beta right now so the API can still change):

  import logging
  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  Setup Sentry SDK to send log messages with a level of "error" or higher to Sentry.
  sentry_sdk.init(
  dsn="...",
  _experiments={
  "enable_sentry_logs": True
  }
  integrations=[
  LoggingIntegration(sentry_logs_level=logging.ERROR),
  ]
  )
  Your existing logging setup
  some_logger = logging.Logger("some-logger")
  some_logger.info('In this example info events will not be sent to Sentry logs. my_value=%s', my_value)
  some_logger.error('But error events will be sent to Sentry logs. my_value=%s', my_value)

• Spotlight: Sample everything 100% w/ Spotlight & no DSN set (#4207) by @​BYK

• Dramatiq: use set_transaction_name (#4175) by @​timdrijvers

... (truncated)

Commits

• d42e632 Updated changelog
• d7cf510 release: 2.25.1
• c254ba4 feat(ourlogs): Add a class which batches groups of logs together. (#4229)
• 438ee01 Debug output from Sentry logs should always be debug level. (#4224)
• e4b8dae fix(ai): Do not consume anthropic streaming stop (#4232)
• 8b40aa0 fix(ourlogs): Use repr instead of json for message and arguments (#4227)
• 2dde2fe build(deps): bump actions/create-github-app-token from 1.11.7 to 1.12.0 (#4214)
• d0d70a5 feat: Do not spam sentry_sdk.warnings logger w/ Spotlight (#4219)
• 4dcd538 fixed code snippet (#4218)
• ee97003 Merge branch 'release/2.25.0'
• 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)