Bump sentry-sdk from 2.55.0 to 2.68.1

[dependabot]

Bumps sentry-sdk from 2.55.0 to 2.68.1.

Release notes

Sourced from sentry-sdk's releases.

2.68.1

enable_logs

• (logs) Don't stop sending auto-collected logs when enable_logs=True by @​sentrivana in #7237

  If you have enable_logs set to True, our logging integrations for the standard library logging module as well as Loguru will auto-collect logs and send them to Sentry as Sentry logs by default, preserving old behavior. Turning automatic collection off for a specific integration can still be achieved using the capture_sentry_logs integration option.

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  enable_logs=True,
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=False),
  ],
  )

  Please note that the enable_logs option is deprecated and will be removed in the next major release. The sentry_sdk.logger.X API now works regardless of it, and auto-collection can be opted into via the capture_sentry_logs integration-level options, which are False by default, unless you have enable_logs=True. We've added this compatibility layer to make the transition to a enable_logs-free world easier.

Bug Fixes 🐛

• (django) Add failed_request_status_codes by @​mgaligniana in #7140
• (anthropic) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7207
• (google_genai) Gate streaming gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7210
• (langchain) Use gen_ai.tool.definitions attribute when data collection is enabled by @​ericapisani in #7204
• (langgraph,huggingface_hub) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7208
• (openai) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7205
• (openai_agents) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7209

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.68.1

enable_logs

• (logs) Don't stop sending auto-collected logs when enable_logs=True by @​sentrivana in #7237

  If you have enable_logs set to True, our logging integrations for the standard library logging module as well as Loguru will auto-collect logs and send them to Sentry as Sentry logs by default, preserving old behavior. Turning automatic collection off for a specific integration can still be achieved using the capture_sentry_logs integration option.

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  enable_logs=True,
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=False),
  ],
  )

  Please note that the enable_logs option is deprecated and will be removed in the next major release. The sentry_sdk.logger.X API now works regardless of it, and auto-collection can be opted into via the capture_sentry_logs integration-level options, which are False by default, unless you have enable_logs=True. We've added this compatibility layer to make the transition to a enable_logs-free world easier.

Bug Fixes 🐛

• (django) Add failed_request_status_codes by @​mgaligniana in #7140
• (anthropic) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7207
• (google_genai) Gate streaming gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7210
• (langchain) Use gen_ai.tool.definitions attribute when data collection is enabled by @​ericapisani in #7204
• (langgraph,huggingface_hub) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7208
• (openai) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7205
• (openai_agents) Gate gen_ai.response.tool_calls on outputs, not inputs by @​ericapisani in #7209

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

... (truncated)

Commits

• 98f7d91 Update changelog
• 8f886ff release: 2.68.1
• df4ec02 fix(logs): Don't stop sending auto-collected logs when enable_logs=True (#7...
• e320318 test(pyramid): Add tests for data_collection gating of request body (#7218)
• 7b8a385 test(bottle): Add tests for data_collection gating of request body (#7217)
• cbcadc9 test(sanic): Add tests for data_collection gating of request body (#7216)
• e42c798 feat(tornado): Gate request body collection on data_collection option (#7215)
• d05bb60 test(django): Add tests for data_collection gating of request body (#7213)
• bcce67b feat(wsgi): Gate request body collection on data_collection option (#7212)
• 41220c4 fix(google_genai): Gate streaming gen_ai.response.tool_calls on outputs, no...
• 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 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)

[rtibblesbot]

🟡 Waiting for changes

Last updated: 2026-09-01 00:46 UTC

[rtibblesbot]

PR #733 — sentry-sdk 2.55.0 → 2.68.1, lockfile-only.

• Semver risk: minor (13 accumulated minor releases)
• Dependency type: production, optional extra — sentry = ["sentry-sdk>=2.32.0"] already admits 2.68.1, so no manifest change is needed
• Breaking changes: none reaching this project
• Security fixes: none for consumers (the one (security) entry is a script-injection fix in sentry-python's own CI workflow)
• Peer/transitive deps: unchanged (certifi, urllib3>=1.26.11); lockfile diff is confined to the sentry-sdk block
• CI: passing across the full 3.9–3.13 × ubuntu/macos/windows matrix

Behavior changes in range, none of which apply here — ricecooker's only usage is a bare sentry_sdk.init() with no arguments (ricecooker/config.py:288):

• 2.68.0 made enable_logs/enable_metrics no-op (to be dropped next major), with 2.68.1 partially reverting; neither option is set here.
• 2.61.1 disabled event string truncation by default — very large payloads may be dropped rather than truncated.
• 2.64.0 gen_ai span changes and the send_default_pii gating sweep affect only AI/web-framework integrations, none installed.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

• Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
• Extracted the changelog and release notes across the version range
• Assessed compatibility with this project's usage and whether any code changes are required
• Treated CI as the primary safety net
• Scaled the review depth to the update's risk
• Chose the verdict from semver risk, changelog findings, and CI status