Bump sentry from 0.37.0 to 0.39.0

[dependabot]

Bumps sentry from 0.37.0 to 0.39.0.

Release notes

Sourced from sentry's releases.

0.39.0

Logs

Support for Sentry structured logs has been added to the SDK.

• To set up logs, enable the logs feature of the sentry crate and set enable_logs to true in your client options.
• Then, use the logger_trace!, logger_debug!, logger_info!, logger_warn!, logger_error! and logger_fatal! macros to capture logs.
• To filter or update logs before they are sent, you can use the before_send_log client option.
• Please note that breaking changes could occur until the API is finalized.

Features

• feat(logs): add log protocol types (#821) by @​lcian
• feat(logs): add ability to capture and send logs (#823) by @​lcian & @​Swatinem
• feat(logs): add macro-based API (#827) by @​lcian & @​szokeasaurusrex
• feat(logs): send logs in batches (#831) by @​lcian

Behavioral changes

• refactor(core): remove support for traceparent (#807) by @​lcian
  • The SDK doesn't support parsing the traceparent distributed tracing header anymore. This means that continue_from_headers (and, as a consequence, parse_headers) will only take into account the sentry-trace header from now on.
  • If you need to continue traces based on the information in the traceparent header, please parse the information from it and then use the API to manually create the desired transaction.
• feat(core): implement Tracing without Performance (#811) by @​lcian
  • The SDK now implements Tracing without Performance, which makes it so that each Scope is associated with an object holding some tracing information.
  • This information is used as a fallback when capturing an event with tracing disabled or otherwise no ongoing span, to still allow related events to be linked by a trace.
  • A new API Scope::iter_trace_propagation_headers has been provided that will use the fallback tracing information if there is no current Span on the Scope.

Breaking changes

• refactor: remove debug-logs feature (#820) by @​lcian
  • The deprecated debug-logs feature of the sentry crate, used for the SDK's own internal logging, has been removed.

0.38.1

Fixes

• build: include sentry-actix optionally when release-health is enabled (#806) by @​lcian
  • sentry-actix is now being included as a dependency only when explicitly added, either as a direct dependency or through the actix feature flag of the sentry crate.
  • Due to a mistake in the Cargo.toml, it was previously being included as a dependency by default when using just the sentry crate with default features.

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

... (truncated)

Changelog

Sourced from sentry's changelog.

0.39.0

Features

Support for Sentry structured logs has been added to the SDK.

• To set up logs, enable the logs feature of the sentry crate and set enable_logs to true in your client options.

• Then, use the logger_trace!, logger_debug!, logger_info!, logger_warn!, logger_error! and logger_fatal! macros to capture logs.

• To filter or update logs before they are sent, you can use the before_send_log client option.

• Please note that breaking changes could occur until the API is finalized.

• feat(logs): add log protocol types (#821) by @​lcian

• feat(logs): add ability to capture and send logs (#823) by @​lcian & @​Swatinem

• feat(logs): add macro-based API (#827) by @​lcian & @​szokeasaurusrex

• feat(logs): send logs in batches (#831) by @​lcian

Behavioral changes

• feat(core): implement Tracing without Performance (#811) by @​lcian
  • The SDK now implements Tracing without Performance, which makes it so that each Scope is associated with an object holding some tracing information.
  • This information is used as a fallback when capturing an event with tracing disabled or otherwise no ongoing span, to still allow related events to be linked by a trace.
  • A new API Scope::iter_trace_propagation_headers has been provided that will use the fallback tracing information if there is no current Span on the Scope.

Breaking changes

• refactor: remove debug-logs feature (#820) by @​lcian
  • The deprecated debug-logs feature of the sentry crate, used for the SDK's own internal logging, has been removed.

0.38.1

Fixes

• build: include sentry-actix optionally when release-health is enabled (#806) by @​lcian
  • sentry-actix is now being included as a dependency only when explicitly added, either as a direct dependency or through the actix feature flag of the sentry crate.
  • Due to a mistake in the Cargo.toml, it was previously being included as a dependency by default when using just the sentry crate with default features.

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.

... (truncated)

Commits

• 37dda6b release: 0.39.0
• cb7fc81 feat(logs): send logs in batches (#831)
• 5912203 chore: cargo +nightly clippy --fix (#833)
• be2e04e feat(logs): add macro-based API (#827)
• d668e7d feat(logs): add ability to capture and send logs (#823)
• 7abbb38 feat(logs): add log protocol types (#821)
• 9c65afe fix: fix clippy lints on stable (#822)
• cb7be0e feat(core): implement Tracing without Performance (#811)
• ae9779f refactor: remove debug-logs feature (#820)
• b3d1d59 build: remove some unused dependencies (#819)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 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)