Skip to content

chore(deps): update dependency sentry-sdk to v2 - #60

Open
renovate[bot] wants to merge 1 commit into
dmdatafrom
renovate/sentry-sdk-2.x
Open

chore(deps): update dependency sentry-sdk to v2#60
renovate[bot] wants to merge 1 commit into
dmdatafrom
renovate/sentry-sdk-2.x

Conversation

@renovate

@renovate renovate Bot commented Sep 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
sentry-sdk (changelog) ~=1.39.2 → ~=2.69.2 age confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.69.2

Compare Source

Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧
Huggingface Hub
Pydantic Ai
Other
Other

v2.69.1

Compare Source

New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
Mcp
Other

v2.69.0

Compare Source

New Features ✨
Other
Bug Fixes 🐛
Mcp
Openai
Starlette
Other
Internal Changes 🔧
Openai Agents
Pydantic Ai
Other

v2.68.1

Compare Source

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 🐛

v2.68.0

Compare Source

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

sentry_sdk.init(
    integrations=[
        LoggingIntegration(capture_sentry_logs=True),
        LoguruIntegration(capture_sentry_logs=True),
    ],
)

If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.
Why We're Doing This

We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨
Other
Bug Fixes 🐛
Internal Changes 🔧
HTTPX, HTTPX2
Other

v2.67.1

Compare Source

Bug Fixes 🐛

v2.67.0

Compare Source

New Features ✨
Batcher
Integrations
Langchain
Openai
Streaming
Other
Bug Fixes 🐛
Openai Agents
Tests
Other
Documentation 📚
Internal Changes 🔧
Fastmcp
Mcp
Openai Agents
Other

v2.66.1

Compare Source

Bug Fixes 🐛
Tracing
Internal Changes 🔧

v2.66.0

Compare Source

New Features ✨
Bug Fixes 🐛
Tracing
Internal Changes 🔧

v2.65.0

Compare Source

New Features ✨
Huey
Other
Bug Fixes 🐛
Tracing
Other
Internal Changes 🔧

v2.64.0

Compare Source

The SDK now extracts all gen_ai spans out of a transaction and sends them as v2 envelope items by default. This prevents gen_ai spans from being dropped when the transaction payload exceeds size limits. Because they are no longer constrained by transaction size limits, AI message data is also no longer truncated. To keep the previous behavior, set stream_gen_ai_spans=False.

Self-hosted Sentry users should opt out with stream_gen_ai_spans=False, since streamed gen_ai spans may not be ingested by their Sentry instance.

Bug Fixes 🐛

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch 2 times, most recently from 55d4cc4 to fdf46e1 Compare September 8, 2026 15:51
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from fdf46e1 to ee142db Compare September 15, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants