Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 18 commits
- 46 files changed
- 7 contributors
Commits on Nov 11, 2025
Commits on Nov 12, 2025
-
* setup external propagation context to fetch `trace_id/span_id` from otel * setup otlp exporter with endpoint and headers taken from DSN * setup propagator * exporter and propagator are setup by default, can be turned off in case people want to setup manually ### Issues * resolves #4935 * resolves PY-1894
Commits on Nov 13, 2025
-
-
feat(integrations): implement context management for invoke_agent spa…
…ns (#5089) - Introduced context variables to manage nested invoke_agent spans safely. - Added functions to push and pop spans from the context stack. - Updated existing code to utilize context variables instead of Sentry scope for agent management. - Enhanced execute_tool_span to support parent-child relationships between spans. This change improves the handling of agent spans during nested calls, ensuring better traceability and isolation of spans in asynchronous contexts. ### Description <!-- What changed and why? --> #### Issues * Closes https://linear.app/getsentry/issue/TET-1388/pydantic-ai-replace-current-scope-context-with-contextvar * Closes https://linear.app/getsentry/issue/TET-1373/pydantic-ai-wrong-hierarchy-of-execute-tool-spans #### Reminders - Please add tests to validate your changes, and lint your code using `tox -e linters`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr)
-
Commits on Nov 14, 2025
-
fix(ci): Re-enable skipped tests (#5104)
### Description We had to resort to skipping two tests in https://github.com/getsentry/sentry-python/pull/5088/files since they were blocking the release. Re-enabling them here. It looks like the worst of the flakiness comes with newer coverage (>=7.11.1). Pinning it here. #### Issues Closes #5101 Closes https://linear.app/getsentry/issue/PY-1974/fix-skipped-tests #### Reminders - Please add tests to validate your changes, and lint your code using `tox -e linters`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr)
Commits on Nov 17, 2025
-
ci: 🤖 Update test matrix with new releases (11/17) (#5110)
Update our test matrix with new releases of integrated frameworks and libraries. ## How it works - Scan PyPI for all supported releases of all frameworks we have a dedicated test suite for. - Pick a representative sample of releases to run our test suite against. We always test the latest and oldest supported version. - Update [tox.ini](https://github.com/getsentry/sentry-python/blob/master/tox.ini) with the new releases. ## Action required - If CI passes on this PR, it's safe to approve and merge. It means our integrations can handle new versions of frameworks that got pulled in. - If CI doesn't pass on this PR, this points to an incompatibility of either our integration or our test setup with a new version of a framework. - Check what the failures look like and either fix them, or update the [test config](https://github.com/getsentry/sentry-python/blob/master/scripts/populate_tox/config.py) and rerun [scripts/generate-test-files.sh](https://github.com/getsentry/sentry-python/blob/master/scripts/generate-test-files.sh). See [scripts/populate_tox/README.md](https://github.com/getsentry/sentry-python/blob/master/scripts/populate_tox/README.md) for what configuration options are available. _____________________ _🤖 This PR was automatically created using [a GitHub action](https://github.com/getsentry/sentry-python/blob/master/.github/workflows/update-tox.yml)._ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>
-
chore: add MCP SDK Pydantic AI and OpenAI Agents to the list of auto …
…enabled integrations (#5111) Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>
-
chore(toxgen): Check availability of pip and add detail to exceptions (…
…#5076) Exit `populate_tox.py` early if `pip` module is not available, and add a suggestion for running the script.
Configuration menu
Commits on Nov 18, 2025
-
fix(logs): Update
sentry.origin(#5112)### Description See #4907 #### Issues Closes #4907 Closes https://linear.app/getsentry/issue/PY-1878/ensure-the-python-sdk-sets-sentryorigin-for-structured-logs-according #### Reminders - Please add tests to validate your changes, and lint your code using `tox -e linters`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr)
-
chore: Deprecate
max_spansLangChain parameter (#5074)Set the default value of the `max_spans` parameter of `LangchainIntegration` to `None`, so that LangChain spans are not exited early by default. Deprecate the parameter and announce its removal in the next major release. Closes #4985
-
chore: Deprecate description truncation option for Redis spans (#5073)
Set the default value of the `max_data_size` parameter of `RedisIntegration` to `None`, so that Redis span descriptions are not truncated by default. Deprecate the parameter and announce its removal in the next major release. Closes #4990
-
feat: Attach
server.addressto metrics (#5113)Set the `server.address` attribute on metrics analogously to logs. https://linear.app/getsentry/issue/SDK-60/attach-serveraddress-as-a-default-attribute-to-metrics.
-
test: add tests for either FastMCP implementation (#5075)
#### Issues Closes https://linear.app/getsentry/issue/TET-1329/fastmcp-tests #### Reminders - Please add tests to validate your changes, and lint your code using `tox -e linters`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr)
-
fix(integrations): ensure that GEN_AI_AGENT_NAME is properly set for …
…GEN_AI spans under an invoke_agent span (#5030) ### Description chat and execute tool spans under an invoke agent span should have the agent name property set #### Issues Closes https://linear.app/getsentry/issue/TET-1293/make-sure-that-agent-name-is-set-on-all-of-its-gen-ai-children --------- Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>
-
fix: Cast message and detail attributes before appending exception no…
…tes (#5114) Cast `message` and `detail` attributes on exceptions to string before generating the `value` of the Sentry exception. Prevents an unhandled `TypeError` when these attributes are `bytes`, as `get_error_message()` attempts to append string exception notes. Resolves the exception described in #5050.
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 2.44.0...2.45.0