Bump sentry/sentry from 4.20.0 to 4.21.0 in /_backend

[dependabot]

Bumps sentry/sentry from 4.20.0 to 4.21.0.

Release notes

Sourced from sentry/sentry's releases.

4.21.0

The Sentry SDK team is happy to announce the immediate availability of Sentry PHP SDK v4.21.0.

Features

• Add RuntimeContext and context lifecycle helpers for long-lived runtimes such as FrankenPHP and RoadRunner. [(#2011)](getsentry/sentry-php#2011)

Long-lived worker runtimes keep process memory between requests, which can cause scope data to leak from one request to the next. RuntimeContext isolates SDK state per request and flushes buffered telemetry when the request context ends. Data configured before a runtime context is started is copied into each new context as baseline scope data.

Example:

\Sentry\init([
    'dsn' => '__YOUR_DSN__',
]);
$handler = static function (): void {
\Sentry\withContext(static function (): void {
// Handle one request.
});
};
while (frankenphp_handle_request($handler)) {}

When using a runtime context, manual \Sentry\flush() calls are not needed for request teardown. It is still necessary to finish transactions explicitly.

Changelog

Sourced from sentry/sentry's changelog.

4.21.0

The Sentry SDK team is happy to announce the immediate availability of Sentry PHP SDK v4.21.0.

Features

• Add RuntimeContext and context lifecycle helpers for long-lived runtimes such as FrankenPHP and RoadRunner. [(#2011)](getsentry/sentry-php#2011)

Long-lived worker runtimes keep process memory between requests, which can cause scope data to leak from one request to the next. RuntimeContext isolates SDK state per request and flushes buffered telemetry when the request context ends. Data configured before a runtime context is started is copied into each new context as baseline scope data.

Example:

\Sentry\init([
    'dsn' => '__YOUR_DSN__',
]);
$handler = static function (): void {
\Sentry\withContext(static function (): void {
// Handle one request.
});
};
while (frankenphp_handle_request($handler)) {}

When using a runtime context, manual \Sentry\flush() calls are not needed for request teardown. It is still necessary to finish transactions explicitly.

Commits

• 2bf405f release: 4.21.0
• 4e60cfe Prepare 4.21.0 (#2015)
• 10d2347 feat: add runtime context to improve support for FrankenPHP and RoadRunner (#...
• 9f8eff4 chore(deps): bump getsentry/craft from 2.19.0 to 2.21.4 (#2010)
• e553a16 Merge branch 'release/4.20.0'
• See full diff 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)