Skip to content

Commit

Permalink
chore: update changelog for version 3.2.0 (#12655)
Browse files Browse the repository at this point in the history
- [x] update changelog for version 3.2.0

---------

Co-authored-by: Emmett Butler <[email protected]>
  • Loading branch information
juanjux and emmettbutler authored Mar 6, 2025
1 parent 598d4ac commit 351de15
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,28 @@

Changelogs for versions not listed here can be found at https://github.com/DataDog/dd-trace-py/releases

---

## 3.2.0

### New Features


- ASM: This introduces auto instrumentation of signup events for Django.
### Upgrade Notes

- ASM: To align across products, we're replacing `DD_EXPERIMENTAL_APPSEC_STANDALONE_ENABLED` with `DD_APM_TRACING_ENABLED`. Feature set remains the same.
- Bumps libdatadog dependency to v16.0.3.

### Bug Fixes

- celery: When multiple broker URLs are provided as a list, use the first broker URL from a list to avoid parsing errors.
- CI Visibility: This fix resolves an issue where ddtrace's own sys.monitoring coverage tool in Python 3.12+ would block other sys.monitoring tools such as pytest-cov from being used.
- tracing: Changes the name of the span event generated by a record\_exception call as it was not following OTEL semantics.
- Fixes an issue where Profiling native threads would respect the musl libc default stack size, which could cause stack overflows in certain configurations.
- profiling: The memory profiler has a guard to avoid re-entering its code if there are allocations during sampling. This guard was meant to be thread-local, but was not correctly declared as such. This doesn't immediately cause problems because the profiler uses try-locks to protect access to its data structures, and re-entering the code will fail to acquire the locks. But this bug could be a source of deadlocks or data corruption if the code changes substantially in the future. This fix makes the guard thread-local as originally intended.


---

## 3.1.0
Expand Down

0 comments on commit 351de15

Please sign in to comment.