Sourced from sentry's releases.

0.38.0

OpenTelemetry integration

An OpenTelemetry integration has been released. Please refer to the changelog entry below for the details.

Breaking changes

• refactor(tracing): remove EventFilter::exception and always attach exception (#768) by @​lcian
  • The EventFilter::Exception enum variant has been removed. Please use EventFilter::Event instead to achieve the same behavior.
  • Using EventFilter::Event will always attach any error struct used within the error field passed to the tracing macro, as EventFilter::Exception did previously.
  • The error field will also be attached to breadcrumbs as an errors field resembling the structure of Sentry events created from error structs.
• fix: use release-health flag in sentry-actix and remove it from subcrates where unneeded (#787) by @​lcian
  • 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.
  • If you depend on sentry with default-features = false, you need to include the release-health feature flag to benefit from the Release Health features of Sentry and have access to the aforementioned client options.
  • The release-health feature flag is used correctly in sentry-actix to enable compilation of that subcrate when it's disabled.
  • The release-health has been removed from the sentry-tracing and sentry-tower subcrates, where it was unnecessary.
• refactor: remove Surf transport (#766) by @​lcian
  • The Surf transport has been removed as the surf crate is unmaintained and it was holding back dependency upgrades.
  • If you really want to still use Surf, you can define a custom TransportFactory and pass it as the transport in your ClientOptions

Behavioral changes

• refactor: honor send_default_pii in sentry-actix and sentry-tower (#771) by @​lcian
  • The client option send_default_pii (disabled by default) is now honored by sentry-actix and sentry-tower.
  • 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.
  • If you want to get back to the previous behavior and capture all headers, please set send_default_pii to true in your ClientOptions.
  • Please refer to our Data Collected page for a comprehensive view of the data collected by the SDK.
• refactor(debug-images): force init DEBUG_META on integration init (#773) by @​lcian
  • The DebugImages integration has been updated to init the DEBUG_META Lazy immediately.
  • Using this integration is known to cause issues in specific versions of the Linux kernel due to issues in a library it depends on.
  • 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.

Features

• feat(otel): add OpenTelemetry SpanProcessor, Propagator, Extractor (#779) by @​lcian
  • A new integration for the opentelemetry crate has been released.
  • It can be used to capture spans created using the opentelemetry API and send them to Sentry.
  • Distributed tracing is also supported, provided that the upstream/downstream services support the Sentry or W3C distributed tracing metadata format.
  • Please refer to the subcrate's README or the crate docs to see an example of setup and usage.
• feat: expose sentry-actix as a feature of sentry (#788) by @​lcian
  • sentry-actix is now exposed by the sentry crate as sentry::integrations::actix, gated behind the actix feature flag.
  • Please update your dependencies to not depend on the sentry-actix subcrate directly.

Dependencies

• build(deps): bump openssl from 0.10.71 to 0.10.72 (#762) by @​dependabot
• build(deps): bump tokio from 1.44.1 to 1.44.2 (#763) by @​dependabot
• chore(deps): bump some dependencies and update Cargo.lock (#772) by @​lcian

Various fixes & improvements

... (truncated)

Sourced from sentry's changelog.

0.38.0

OpenTelemetry integration

An OpenTelemetry integration has been released. Please refer to the changelog entry below for the details.

Breaking changes

• refactor(tracing): remove EventFilter::exception and always attach exception (#768) by @​lcian
  • The EventFilter::Exception enum variant has been removed. Please use EventFilter::Event instead to achieve the same behavior.
  • Using EventFilter::Event will always attach any error struct used within the error field passed to the tracing macro, as EventFilter::Exception did previously.
  • The error field will also be attached to breadcrumbs as an errors field resembling the structure of Sentry events created from error structs.
• fix: use release-health flag in sentry-actix and remove it from subcrates where unneeded (#787) by @​lcian
  • 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.
  • If you depend on sentry with default-features = false, you need to include the release-health feature flag to benefit from the Release Health features of Sentry and have access to the aforementioned client options.
  • The release-health feature flag is used correctly in sentry-actix to enable compilation of that subcrate when it's disabled.
  • The release-health has been removed from the sentry-tracing and sentry-tower subcrates, where it was unnecessary.
• refactor: remove Surf transport (#766) by @​lcian
  • The Surf transport has been removed as the surf crate is unmaintained and it was holding back dependency upgrades.
  • If you really want to still use Surf, you can define a custom TransportFactory and pass it as the transport in your ClientOptions

Behavioral changes

• refactor: honor send_default_pii in sentry-actix and sentry-tower (#771) by @​lcian
  • The client option send_default_pii (disabled by default) is now honored by sentry-actix and sentry-tower.
  • 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.
  • If you want to get back to the previous behavior and capture all headers, please set send_default_pii to true in your ClientOptions.
  • Please refer to our Data Collected page for a comprehensive view of the data collected by the SDK.
• refactor(debug-images): force init DEBUG_META on integration init (#773) by @​lcian
  • The DebugImages integration has been updated to init the DEBUG_META Lazy immediately.
  • Using this integration is known to cause issues in specific versions of the Linux kernel due to issues in a library it depends on.
  • 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.

Features

• feat(otel): add OpenTelemetry SpanProcessor, Propagator, Extractor (#779) by @​lcian
  • A new integration for the opentelemetry crate has been released.
  • It can be used to capture spans created using the opentelemetry API and send them to Sentry.
  • Distributed tracing is also supported, provided that the upstream/downstream services support the Sentry or W3C distributed tracing metadata format.
  • Please refer to the subcrate's README or the crate docs to see an example of setup and usage.
• feat: expose sentry-actix as a feature of sentry (#788) by @​lcian
  • sentry-actix is now exposed by the sentry crate as sentry::integrations::actix, gated behind the actix feature flag.
  • Please update your dependencies to not depend on the sentry-actix subcrate directly.

Dependencies

• build(deps): bump openssl from 0.10.71 to 0.10.72 (#762) by @​dependabot
• build(deps): bump tokio from 1.44.1 to 1.44.2 (#763) by @​dependabot
• chore(deps): bump some dependencies and update Cargo.lock (#772) by @​lcian

... (truncated)

• 8d72c98 release: 0.38.0
• f41d60a build(otel): exclude version from circular dev-dependencies (#802)
• 7074891 fix(otel): fix span and trace ids for distributed tracing (#801)
• 69ce481 chore: prepare changelog for 0.38 release (#800)
• 1de559b fix(otel): fix doctests (#794)
• b69d82a fix: use release-health flag in sentry-actix and remove it from subcrates...
• c3987a6 docs: update docs including OTEL and other integrations (#790)
• 701c358 feat: expose sentry-actix as a feature of sentry (#788)
• 2eb09ec build: add sentry-opentelemetry to workspace (#789)
• 3cc461a feat(otel): add OpenTelemetry SpanProcessor, Propagator, Extractor (#779)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)