Repository navigation
Support sentry-sdk 3.x once 3.0 is GA #380
Copy link
Copy link
Open
Labels
blockedWaiting on an external dependency or upstream changeWaiting on an external dependency or upstream changeenhancementNew feature or requestNew feature or request
Description
Blocked until sentry-sdk 3.0 is released as GA. 3.0.0b2 (2026-10-27) is the latest release on PyPI today, and the 3.0 release notes plan GA for November 2026.
#359 added support for 3.x alongside 2.x and tested it against 3.0.0b2. #379 removed that support, so lite-bootstrap 2.0 can ship before GA with sentry-sdk>=2.70,<3. The betas were still changing: b2 kept trace_lifecycle, which b1's migration guide listed as removed, and it removed enable_metrics, stream_gen_ai_spans and trace_ignore_status_codes. This issue brings 3.x support back against the GA release. It doesn't break 2.x users, so it can ship in a 2.x minor.
Work
- Start from Cap sentry-sdk below 3 and remove the 3.x code paths #379's diff, which records every 3.x path that was removed. Then check each one against the GA migration guide rather than restoring it blindly:
LoggingIntegration: on 3.x,levelmeans Sentry Logs andevent_leveldefaults toNone. feat(sentry)!: support sentry-sdk 3 alongside 2.x and raise the floor to 2.70 #359 builtbreadcrumb_level=sentry_logging_breadcrumb_level, event_level=logging.ERROR, level=Noneon 3.x.ignore_loggernow silences Sentry Logs only, and its 2.x meaning moved toignore_logger_for_events. Litestar's lean capture calls it for"litestar".event_from_exceptiontook noclient_optionson 3.0.0b2.LoggingIntegrationis no longer a default integration on 3.x. lite-bootstrap appends its own whilesentry_default_integrationsis True.- Options 3.0 removes raise
TypeError("Unknown option ...")atsentry_sdk.init. Recheck the final list, and checkDEFAULT_DATA_COLLECTIONagainst GA'sdata_collectionkeys.
- Test first: run the suite against the GA release and record what fails.
pyproject.toml:sentry-sdk>=2.70,<4, and rewrite the comment above it.- CI: bring back a job that runs the suite on
sentry-sdk<3, because thepytestjobs will resolve 3.x once it is GA. Pin the other leg to the GA version, or let it resolve the newest 3.x. - Benchmarks: make
micro.py,repro_sentry_txn.pyandsentry_scenarios.pyrun on both majors again, as feat(sentry)!: support sentry-sdk 3 alongside 2.x and raise the floor to 2.70 #359 did. On 3.x, no transaction is built while tracing is off. - Docs: restore the per-major
LoggingIntegrationcall and the note on removed options inconfiguration.md. Remeasure the Sentry cost tables infastapi.md,litestar.mdandfastmcp.mdon GA, and add a 3.x column.
Verify: the suite passes on the newest 2.x and on the 3.0 GA release, and ty check passes against both.
Metadata
Metadata
Assignees
Labels
blockedWaiting on an external dependency or upstream changeWaiting on an external dependency or upstream changeenhancementNew feature or requestNew feature or request
Activity