Skip to content

Commit 69ce481

Browse files
authored
chore: prepare changelog for 0.38 release (#800)
* chore: prepare changelog for 0.38 release * update * update * reorder
1 parent 1de559b commit 69ce481

File tree

1 file changed

+60
-0
lines changed

1 file changed

+60
-0
lines changed

CHANGELOG.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,65 @@
11
# Changelog
22

3+
## Unreleased
4+
5+
### OpenTelemetry integration
6+
7+
An OpenTelemetry integration has been released. Please refer to the changelog entry below for the details.
8+
9+
### Breaking changes
10+
11+
- refactor(tracing): remove `EventFilter::exception` and always attach exception (#768) by @lcian
12+
- The `EventFilter::Exception` enum variant has been removed. Please use `EventFilter::Event` instead to achieve the same behavior.
13+
- Using `EventFilter::Event` will always attach any error struct used within the `error` field passed to the `tracing` macro, as `EventFilter::Exception` did previously.
14+
- The `error` field will also be attached to breadcrumbs as an `errors` field resembling the structure of Sentry events created from error structs.
15+
- fix: use `release-health` flag in `sentry-actix` and remove it from subcrates where unneeded (#787) by @lcian
16+
- As a follow-up from the changes in the previous release, the `ClientOptions` fields `auto_session_tracking` and `session_mode` are now gated behind the `release-health` feature flag of the `sentry` crate.
17+
- If you depend on `sentry` with `default-features = false`, you need to include the `release-health` feature flag to benefit from the [Release Health](https://docs.sentry.io/product/releases/health/) features of Sentry and have access to the aforementioned client options.
18+
- The `release-health` feature flag is used correctly in `sentry-actix` to enable compilation of that subcrate when it's disabled.
19+
- The `release-health` has been removed from the `sentry-tracing` and `sentry-tower` subcrates, where it was unnecessary.
20+
- refactor: remove Surf transport (#766) by @lcian
21+
- The Surf transport has been removed as the `surf` crate is unmaintained and it was holding back dependency upgrades.
22+
- If you really want to still use Surf, you can define a custom `TransportFactory` and pass it as the `transport` in your `ClientOptions`
23+
24+
### Behavioral changes
25+
26+
- refactor: honor `send_default_pii` in `sentry-actix` and `sentry-tower` (#771) by @lcian
27+
- The client option `send_default_pii` (disabled by default) is now honored by `sentry-actix` and `sentry-tower`.
28+
- This means that potentially sensitive headers such as authorization, cookies, and those that usually contain the user's IP address are filtered and not sent to Sentry.
29+
- If you want to get back to the previous behavior and capture all headers, please set `send_default_pii` to `true` in your `ClientOptions`.
30+
- Please refer to our [Data Collected](https://docs.sentry.io/platforms/rust/data-management/data-collected/) page for a comprehensive view of the data collected by the SDK.
31+
- refactor(debug-images): force init `DEBUG_META` on integration init (#773) by @lcian
32+
- The `DebugImages` integration has been updated to init the `DEBUG_META` `Lazy` immediately.
33+
- Using this integration is known to cause issues in specific versions of the Linux kernel due to issues in a library it depends on.
34+
- Previously, on problematic systems the SDK would cause deadlock after capturing the first event. Now the SDK will panic on initialization instead. Please open an issue if you're affected.
35+
36+
### Features
37+
38+
- feat(otel): add OpenTelemetry SpanProcessor, Propagator, Extractor (#779) by @lcian
39+
- A new integration for the `opentelemetry` crate has been released.
40+
- It can be used to capture spans created using the `opentelemetry` API and send them to Sentry.
41+
- Distributed tracing is also supported, provided that the upstream/downstream services support the Sentry or W3C distributed tracing metadata format.
42+
- Please refer to the subcrate's README or the crate docs to see an example of setup and usage.
43+
- feat: expose `sentry-actix` as a feature of `sentry` (#788) by @lcian
44+
- `sentry-actix` is now exposed by the `sentry` crate as `sentry::integrations::actix`, gated behind the `actix` feature flag.
45+
- Please update your dependencies to not depend on the `sentry-actix` subcrate directly.
46+
47+
### Dependencies
48+
49+
- build(deps): bump openssl from 0.10.71 to 0.10.72 (#762) by @dependabot
50+
- build(deps): bump tokio from 1.44.1 to 1.44.2 (#763) by @dependabot
51+
- chore(deps): bump some dependencies and update `Cargo.lock` (#772) by @lcian
52+
53+
### Various fixes & improvements
54+
55+
- Replace `once_cell` with `std::sync::LazyLock` (#776) by @FalkWoldmann
56+
- chore: update GH issue templates for Linear compatibility (#777) by @stephanie-anderson
57+
- chore: update issue templates with blank issue and Discord link (#778) by @lcian
58+
- refactor(core): fail with message if TLS backend not available (#784) by @lcian
59+
- build: add `sentry-opentelemetry` to workspace (#789) by @lcian
60+
- docs: update docs including OTEL and other integrations (#790) by @lcian
61+
- fix(otel): fix doctests (#794) by @lcian
62+
363
## 0.37.0
464

565
### Breaking changes

0 commit comments

Comments
 (0)