Bump sentry/sentry from 1.11.0 to 4.4.0

[dependabot[bot]]

Bumps sentry/sentry from 1.11.0 to 4.4.0.

Release notes

Sourced from sentry/sentry's releases.

4.4.0

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

Features

• Add metrics()->timing() [(#1670)](getsentry/sentry-php#1670)

  This allows you to emit a distribution metric based on the duration of the provided callback.

  use function Sentry\metrics;
  metrics()->timing(
  key: 'my-metric',
  callback: fn() => doSomething(),
  );
  

• Add withMonitor() [(#1679)](getsentry/sentry-php#1679)

  This wraps a callback into monitor check-ins.

  use function Sentry\withMonitor;
  withMonitor(
  slug: 'my-monitor',
  callback: fn () => doSomething(),
  monitorConfig: new MonitorConfig(...),
  );
  

• Add new failure_issue_threshold and recovery_threshold configuration to MonitorConfig [(#1685)](getsentry/sentry-php#1685)

• Add TransactionContext::make() and SpanContext::make() [(#1684)](getsentry/sentry-php#1684)

  use Sentry\Tracing\SpanContext;
  $spanCpntext = SpanContext::make()
  ->setOp('http.client')
  ->setDescription('GET https://example.com')
  

• Add support for fluent use of Transaction::setName() [(#1687)](getsentry/sentry-php#1687)

• Add support for the W3C traceparent header [(#1680)](getsentry/sentry-php#1680)

Bug Fixes

• Do not send an empty event if no metrics are in the bucket [(#1676)](getsentry/sentry-php#1676)

... (truncated)

Changelog

Sourced from sentry/sentry's changelog.

4.4.0

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

Features

• Add metrics()->timing() [(#1670)](getsentry/sentry-php#1670)

  This allows you to emit a distribution metric based on the duration of the provided callback.

  use function Sentry\metrics;
  metrics()->timing(
  key: 'my-metric',
  callback: fn() => doSomething(),
  );
  

• Add withMonitor() [(#1679)](getsentry/sentry-php#1679)

  This wraps a callback into monitor check-ins.

  use function Sentry\withMonitor;
  withMonitor(
  slug: 'my-monitor',
  callback: fn () => doSomething(),
  monitorConfig: new MonitorConfig(...),
  );
  

• Add new failure_issue_threshold and recovery_threshold configuration to MonitorConfig [(#1685)](getsentry/sentry-php#1685)

• Add TransactionContext::make() and SpanContext::make() [(#1684)](getsentry/sentry-php#1684)

  use Sentry\Tracing\SpanContext;
  $spanCpntext = SpanContext::make()
  ->setOp('http.client')
  ->setDescription('GET https://example.com')
  

• Add support for fluent use of Transaction::setName() [(#1687)](getsentry/sentry-php#1687)

• Add support for the W3C traceparent header [(#1680)](getsentry/sentry-php#1680)

Bug Fixes

... (truncated)

Commits

• 95a428a release: 4.4.0
• 1a110bf Prepare 4.4.0 (#1689)
• 4301e89 chore(deps): bump actions/cache from 3 to 4 (#1688)
• 40ddd18 http_ssl_verify_peer sets CURLOPT_SSL_VERIFYPEER correctly (#1686)
• 617dde3 Allow fluent use of Transaction::setName() method (#1687)
• 29d00b0 Add failure_issue_threshold & recovery_threshold to MonitorConfig (#1685)
• a31d418 Add support for W3C traceparent header (#1680)
• 62274fb Add TransactionContext::make() & SpanContext::make() (#1684)
• 1cc36e6 Rename $callable to $callback (#1683)
• 7ac8703 Deprecate user segment (#1681)
• 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 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[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.