-
Notifications
You must be signed in to change notification settings - Fork 583
Comparing changes
Open a pull request
base repository: getsentry/sentry-python
base: 2.52.0
head repository: getsentry/sentry-python
compare: 2.53.0
- 20 commits
- 28 files changed
- 6 contributors
Commits on Feb 4, 2026
-
getsentry-bot committed
Feb 4, 2026 Configuration menu - View commit details
-
Copy full SHA for 4621c29 - Browse repository at this point
Copy the full SHA 4621c29View commit details -
feat(span-streaming): Add more span properties (#5421)
- add setters(/getters) or properties for `op`, `source`, `name`, `origin`, `status`, feature flags, `span_id` - also, rename `name` -> `_name` since it has a getter/setter now In general regarding this getter/setter business vs. property-based getting and setting: The idiomatic way would be to use properties (e.g. `span.name = "name"`), but since we can't get around having _some_ getters/setters (e.g. `set_attribute`, `set_flag`, etc.), it's probably better to go for consistency and have getters/setters everywhere, even if it's not idiomatic. Otherwise users would have to remember if the specific thing they want to set is a property or has a setter. The above is about stuff people might want to set, so public API. For internal stuff that no one should be setting by hand (e.g. `span_id`), we can still go with properties where it makes sense. Chipping away at #5317.
Configuration menu - View commit details
-
Copy full SHA for 3373da2 - Browse repository at this point
Copy the full SHA 3373da2View commit details
Commits on Feb 6, 2026
-
fix(celery): Close the connection we're reading driver_type from (#5427)
Currently, we're reading the driver type (e.g. `redis`) from a connection. We're however not closing the connection, potentially causing file descriptor leaks. **Aside:** Opening a connection just for the purpose of determining the driver type is not ideal in the first place. We should see whether we can get the info from elsewhere from the context of a task's `run`/`__call__` (which is where we're enriching the span with it). Or we could see whether we can cache this somehow. For now, let's at least make sure to clean up the connection. #### Issues Closes #5422 #### 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)
Configuration menu - View commit details
-
Copy full SHA for 1ab6e3d - Browse repository at this point
Copy the full SHA 1ab6e3dView commit details
Commits on Feb 9, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 1476ff0 - Browse repository at this point
Copy the full SHA 1476ff0View commit details
Commits on Feb 10, 2026
-
test: Add test for
get_baggagewith DSN (#5441)For now just testing what CI says about this test
Configuration menu - View commit details
-
Copy full SHA for 18081e7 - Browse repository at this point
Copy the full SHA 18081e7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8f80fa7 - Browse repository at this point
Copy the full SHA 8f80fa7View commit details
Commits on Feb 11, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 1eeb5df - Browse repository at this point
Copy the full SHA 1eeb5dfView commit details
Commits on Feb 12, 2026
-
chore(ci): Improve Craft config with title stripping and artifact fil…
…tering (#5444) ## Summary - Add named regex capture groups to `commit_patterns` in `.github/release.yml` for Craft's [title stripping](https://craft.sentry.dev/configuration/#title-stripping-default-behavior) feature - Remove the CI `merge` job by switching to Craft 2.21.1's [workflow-scoped artifact filtering](https://craft.sentry.dev/configuration/#github-artifact-provider-configuration) (same approach as getsentry/cli#215) - Modernize `.craft.yml` changelog config to object format - Modernize `scripts/bump-version.sh` to use Craft env vars ## Changes ### `.github/release.yml` - All `commit_patterns` now use `(?<type>...)` and `(?<scope>...)` named capture groups so Craft strips conventional commit prefixes from changelog entries - Added **Breaking Changes** category (`semver: major`) from Craft defaults - Expanded Internal Changes patterns to include `refactor|meta|perf` from Craft defaults ### `.craft.yml` - Bumped `minVersion` from `2.17.0` to `2.21.1` - Added `artifactProvider` config to fetch `artifact-*` directly from `ci.yml` workflow - Modernized changelog from separate keys to object format - Added explicit `preReleaseCommand` (was relying on the implicit default) ### `.github/workflows/ci.yml` - Removed the `merge` job (no longer needed with Craft 2.21.1 artifact filtering) - Removed `compression-level: '0'` from upload steps (was only needed for merging) ### `scripts/bump-version.sh` - Use `CRAFT_OLD_VERSION` / `CRAFT_NEW_VERSION` env vars instead of positional arguments (recommended by Craft docs)
Configuration menu - View commit details
-
Copy full SHA for 77035cc - Browse repository at this point
Copy the full SHA 77035ccView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5a8f060 - Browse repository at this point
Copy the full SHA 5a8f060View commit details
Commits on Feb 13, 2026
-
fix(openai-agents): Patch tool functions following library refactor (#…
…5445) `AgentRunner._get_all_tools()` was moved to `agents.run_internal.turn_preparation.get_all_tools()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for b50da06 - Browse repository at this point
Copy the full SHA b50da06View commit details -
ci: Use fixed clickhouse action, remove aws-sam-cli dependency (#5457)
Use https://github.com/getsentry/action-clickhouse-in-ci/releases/tag/v1.7 in our clickhouse test setup. GH environment already has AWS SAM installed with a version compatible with the Docker API offered. --------- Co-authored-by: Alex Alderman Webb <alexander.webb@sentry.io>
Configuration menu - View commit details
-
Copy full SHA for f78df7c - Browse repository at this point
Copy the full SHA f78df7cView commit details -
fix(openai-agents): Patch models functions following library refactor (…
…#5449) `AgentRunner. _get_model()` was moved to `agents.run_internal.turn_preparation. get_model()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for a5c2906 - Browse repository at this point
Copy the full SHA a5c2906View commit details -
fix(openai-agents): Patch
run_single_turn()functions following lib……rary refactor (#5450) `AgentRunner._run_single_turn()` was moved to `agents.run_internal.run_loop.run_single_turn()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for 14e3e0a - Browse repository at this point
Copy the full SHA 14e3e0aView commit details -
fix(openai-agents): Patch
run_single_turn_streamed()functions foll……owing library refactor (#5451) `AgentRunner._run_single_turn_streamed()` was moved to `agents.run_internal.run_loop.run_single_turn_streamed()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for bea608c - Browse repository at this point
Copy the full SHA bea608cView commit details -
fix(openai-agents): Patch
execute_handoffs()functions following li……brary refactor (#5452) `RunImpl.execute_handoffs()` was moved to `agents.run_internal.turn_resolution.execute_handoffs()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for f71a604 - Browse repository at this point
Copy the full SHA f71a604View commit details -
fix(openai-agents): Patch
execute_final_output()functions followin……g library refactor (#5453) `RunImpl.execute_final_output()` was moved to `agents.run_internal.turn_resolution.execute_final_output()`. Patch the new function by reusing existing wrapper logic.
Configuration menu - View commit details
-
Copy full SHA for d3e2c88 - Browse repository at this point
Copy the full SHA d3e2c88View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4d8faf3 - Browse repository at this point
Copy the full SHA 4d8faf3View commit details
Commits on Feb 16, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 45379e2 - Browse repository at this point
Copy the full SHA 45379e2View commit details -
Configuration menu - View commit details
-
Copy full SHA for b700fa8 - Browse repository at this point
Copy the full SHA b700fa8View commit details -
Configuration menu - View commit details
-
Copy full SHA for f75a9ac - Browse repository at this point
Copy the full SHA f75a9acView commit details
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.52.0...2.53.0