Bump sentry from 0.31.5 to 0.37.0

[dependabot]

Bumps sentry from 0.31.5 to 0.37.0.

Release notes

Sourced from sentry's releases.

0.37.0

Breaking changes

• chore(msrv): cargo update and bump MSRV to 1.81 (#754) by @​lcian
  • The minimum supported Rust version has been raised to 1.81.
• feat(core): introduce release-health feature (#749) by @​pepperoni505
  • A new release-health feature flag was introduced that gates the Release Health features of Sentry.
  • This allows for compilation of the SDK on certain WASM targets.
  • Release Health features were already present and enabled with no feature flag in previous versions.
  • The new feature flag will be enabled by default when using sentry, sentry-actix, sentry-tower or sentry-tracing with the default features.
  • If you're fine-tuning your feature flags, make sure to enable release-health to get back the previous behavior.
• ref(metrics): remove features and code related to the old metrics beta (#740) by @​lcian
  • The metrics feature and the code related to it has been removed from the crate, as the Sentry backend stopped ingesting metrics a while ago.
• Switch to MIT license (#724) by @​cleptric
  • The license for the crates has been changed to MIT.

Features

• feat(actix): capture HTTP request body (#731) by @​pacifistes
  • The middleware for actix-web now supports capturing and attaching the request body to HTTP request transactions.
  • You need to enable send_default_pii in your client options for this to be enabled, and you can fine-tune the behavior using the new option max_request_body_size.
• feat(core): transaction.set_data sets data on TraceContext (#739) by @​lcian
  • transaction.set_data now sets data on TraceContext, as the SDK should not use the extra field.
• ref(backtrace): add entries and extra logic for in-app detection (#756) by @​lcian
• feat(core): add more frames to be considered not in_app (#760) by @​lcian
  • The logic used by the SDK to detect in-app stack frames has been improved. Now the SDK will mark more frames as not in-app.
  • A similar improvement has been added to the Sentry backend so that old versions of the SDK can benefit from improved in-app reporting.

Fixes

• fix(http): Finish transaction on drop (#727) by @​Dav1dde
  • Fixed a bug where the current transaction was not finished (hence not sent to Sentry) when its corresponding future was dropped, e.g. due to a panic.
• follow getsentry/sentry-rust#439 for actix-web. fix getsentry/sentry-rust#680 (#737) by @​pavel-rosputko
  • The HTTP request metadata is now being correctly attached to transactions when using sentry-actix.
• fix(tracing): wrap error with synthetic mechanism only if attaching stacktrace (#755) by @​lcian
  • Fixed a bug that should result in improved grouping and issue titles for events reported by sentry-tracing when not capturing stack traces.
• fix(actix): process request in other middleware using correct Hub (#758) by @​lcian
  • The subsequent middleware in the chain when processing a request now execute within the correct Hub.
• fix(anyhow): attach stacktrace only if error provides backtrace (#759) by @​lcian
  • Fixed a bug where the SDK was providing incorrect stack traces when capturing an anyhow when the backtrace feature is enabled but RUST_BACKTRACE is not set.
  • This should result in correct grouping of the affected issues.

Various fixes & improvements

• Fix CS (#726) by @​cleptric
• fix(doctests): update prost (#750) by @​lcian
• chore(msrv): bump MSRV to 1.75 (#751) by @​lcian
• refactor(actix): simplify body_from_http (#757) by @​robjtede
• chore: prepare changelog for release (#761) by @​lcian

... (truncated)

Changelog

Sourced from sentry's changelog.

0.37.0

Breaking changes

• chore(msrv): cargo update and bump MSRV to 1.81 (#754) by @​lcian
  • The minimum supported Rust version has been raised to 1.81.
• feat(core): introduce release-health feature (#749) by @​pepperoni505
  • A new release-health feature flag was introduced that gates the Release Health features of Sentry.
  • This allows for compilation of the SDK on certain WASM targets.
  • Release Health features were already present and enabled with no feature flag in previous versions.
  • The new feature flag will be enabled by default when using sentry, sentry-actix, sentry-tower or sentry-tracing with the default features.
  • If you're fine-tuning your feature flags, make sure to enable release-health to get back the previous behavior.
• ref(metrics): remove features and code related to the old metrics beta (#740) by @​lcian
  • The metrics feature and the code related to it has been removed from the crate, as the Sentry backend stopped ingesting metrics a while ago.
• Switch to MIT license (#724) by @​cleptric
  • The license for the crates has been changed to MIT.

Features

• feat(actix): capture HTTP request body (#731) by @​pacifistes
  • The middleware for actix-web now supports capturing and attaching the request body to HTTP request transactions.
  • You need to enable send_default_pii in your client options for this to be enabled, and you can fine-tune the behavior using the new option max_request_body_size.
• feat(core): transaction.set_data sets data on TraceContext (#739) by @​lcian
  • transaction.set_data now sets data on TraceContext, as the SDK should not use the extra field.
• ref(backtrace): add entries and extra logic for in-app detection (#756) by @​lcian
• feat(core): add more frames to be considered not in_app (#760) by @​lcian
  • The logic used by the SDK to detect in-app stack frames has been improved. Now the SDK will mark more frames as not in-app.
  • A similar improvement has been added to the Sentry backend so that old versions of the SDK can benefit from improved in-app reporting.

Fixes

• fix(http): Finish transaction on drop (#727) by @​Dav1dde
  • Fixed a bug where the current transaction was not finished (hence not sent to Sentry) when its corresponding future was dropped, e.g. due to a panic.
• follow getsentry/sentry-rust#439 for actix-web. fix getsentry/sentry-rust#680 (#737) by @​pavel-rosputko
  • The HTTP request metadata is now being correctly attached to transactions when using sentry-actix.
• fix(tracing): wrap error with synthetic mechanism only if attaching stacktrace (#755) by @​lcian
  • Fixed a bug that should result in improved grouping and issue titles for events reported by sentry-tracing when not capturing stack traces.
• fix(actix): process request in other middleware using correct Hub (#758) by @​lcian
  • The subsequent middleware in the chain when processing a request now execute within the correct Hub.
• fix(anyhow): attach stacktrace only if error provides backtrace (#759) by @​lcian
  • Fixed a bug where the SDK was providing incorrect stack traces when capturing an anyhow when the backtrace feature is enabled but RUST_BACKTRACE is not set.
  • This should result in correct grouping of the affected issues.

Various fixes & improvements

• Fix CS (#726) by @​cleptric
• fix(doctests): update prost (#750) by @​lcian
• chore(msrv): bump MSRV to 1.75 (#751) by @​lcian
• refactor(actix): simplify body_from_http (#757) by @​robjtede
• chore: prepare changelog for release (#761) by @​lcian

... (truncated)

Commits

• 7e6d8cb release: 0.37.0
• 6a8b96d chore: prepare changelog for release (#761)
• 6a0ffeb feat(core): introduce release-health feature (#749)
• 1f0be60 fix(anyhow): attach stacktrace only if error provides backtrace (#759)
• a995b9b feat(core): add more frames to be considered not in_app (#760)
• 44fa0cf fix(actix): process request in other middleware using correct Hub (#758)
• 5dd246d refactor(actix): simplify body_from_http (#757)
• df0491c ref(backtrace): add entries and extra logic for in-app detection (#756)
• e9661c7 fix(tracing): wrap error with synthetic mechanism only if attaching stacktrac...
• 3b73aac chore(msrv): cargo update and bump MSRV to 1.81 (#754)
• 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 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)

[dependabot]

Superseded by #18.