Skip to content

chore(deps): update dependency sentry-sdk to v2.74.0 - #1152

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 15, 2026 •

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) ==2.58.0 → ==2.74.0 age confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.74.0

Compare Source

New Features ✨
Anthropic
Other
Bug Fixes 🐛
Anthropic
Other
Internal Changes 🔧
Deps
Other

v2.73.0

Compare Source

New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
Deps
Other

v2.72.0

Compare Source

New Features ✨
Asgi
Boto3
Wsgi
Other
Bug Fixes 🐛
Boto3
Other
Internal Changes 🔧
Deps
Openai Agents
Starlette
Other

v2.71.0

Compare Source

New Features ✨
import sentry_sdk
from sentry_sdk.integrations.typesafe import TypeSafeIntegration

sentry_sdk.init(
    dsn="...",
    traces_sample_rate=1.0,
    integrations=[
        TypeSafeIntegration(),
    ]
)
Typesafe
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧

v2.70.0

Compare Source

New Features ✨
import sentry_sdk
from sentry_sdk.integrations.mistral import MistralIntegration

sentry_sdk.init(
    dsn="...",
    traces_sample_rate=1.0,
    integrations=[
        MistralIntegration(),
    ]
)
import sentry_sdk

sentry_sdk.init(
    data_collection={
        "user_info": False,
        "gen_ai": {"inputs": False, "outputs": False},
        "graphql": {"document": False, "variables": False},
        "database_query_data": False,
        "queues": False,
        "http_bodies": [],
        "cookies": {
            "mode": "denylist",
            "terms": ["forwarded", "-ip", "remote-", "via", "-user"],
        },
        "http_headers": {
            "request": {
                "mode": "denylist",
                "terms": ["forwarded", "-ip", "remote-", "via", "-user"],
            },
        },
        "url_query_params": {
            "mode": "denylist",
            "terms": ["forwarded", "-ip", "remote-", "via", "-user"],
        },
    }
)
Mistral
Internal Changes 🔧

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 🐛
  • (batcher) Add global

[!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 added the renovate label Jul 15, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from 49b548b to 3d22316 Compare July 16, 2026 13:53
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.65.0 chore(deps): update dependency sentry-sdk to v2.66.0 Jul 16, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch 2 times, most recently from e926bc6 to fb6cdf6 Compare July 22, 2026 17:04
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.66.0 chore(deps): update dependency sentry-sdk to v2.66.1 Jul 22, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from fb6cdf6 to bc39fcb Compare August 10, 2026 15:14
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.66.1 chore(deps): update dependency sentry-sdk to v2.67.1 Aug 10, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from bc39fcb to a6675b9 Compare August 13, 2026 11:44
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.67.1 chore(deps): update dependency sentry-sdk to v2.68.0 Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from a6675b9 to 193eb3b Compare August 25, 2026 15:37
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.68.0 chore(deps): update dependency sentry-sdk to v2.68.1 Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch 3 times, most recently from ba42212 to 3b18ea0 Compare September 8, 2026 10:26
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.68.1 chore(deps): update dependency sentry-sdk to v2.69.0 Sep 8, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from 3b18ea0 to 6eadf08 Compare September 8, 2026 16:00
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.69.0 chore(deps): update dependency sentry-sdk to v2.69.1 Sep 8, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from 6eadf08 to 36d3d1a Compare September 15, 2026 16:53
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.69.1 chore(deps): update dependency sentry-sdk to v2.69.2 Sep 15, 2026
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.69.2 chore(deps): update dependency sentry-sdk to v2.70.0 Sep 22, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch 2 times, most recently from bd34af6 to da1c847 Compare September 28, 2026 22:10
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.70.0 chore(deps): update dependency sentry-sdk to v2.71.0 Sep 28, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from da1c847 to 5c94503 Compare October 13, 2026 00:30
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.71.0 chore(deps): update dependency sentry-sdk to v2.72.0 Oct 13, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from 5c94503 to 3bc0dbf Compare October 22, 2026 10:29
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.72.0 chore(deps): update dependency sentry-sdk to v2.73.0 Oct 22, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-sdk-2.x branch from 3bc0dbf to cc65427 Compare November 5, 2026 15:42
@renovate renovate Bot changed the title chore(deps): update dependency sentry-sdk to v2.73.0 chore(deps): update dependency sentry-sdk to v2.74.0 Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants