fix(deps): update dependency sentry/sentry-symfony to v5 (v4)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sentry/sentry-symfony (source)	^4.2 -> ^5.0

---

Release Notes

getsentry/sentry-symfony (sentry/sentry-symfony)

v5.1.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v5.1.0.

Features

• The SDK was updated to support PHP 8.4 (#​893)
• Set the status for CLI command transactions based on the exit code (#​891)

Bug Fixes

• Fix including request data on transactions (#​879)

v5.0.1

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v5.0.1.

Bug Fixes

• Add missing setCallbackWrapper method to TraceableCacheAdapterTrait (#​841)
• Fix detection of the symfony/http-client being installed (#​858)

v5.0.0

Compare Source

The Sentry SDK team is thrilled to announce the immediate availability of Sentry Symfony SDK v5.0.0.

Breaking Change

Please refer to the UPGRADE-5.0.md guide for a complete list of breaking changes.

This version adds support for the underlying Sentry PHP SDK v4.0.
Please refer to the PHP SDK sentry-php/UPGRADE-4.0.md guide for a complete list of breaking changes.

• This version exclusively uses the envelope endpoint to send event data to Sentry.

  If you are using sentry.io, no action is needed.
  If you are using an on-premise/self-hosted installation of Sentry, the minimum requirement is now version >= v20.6.0.

• You need to have ext-curl installed to use the SDK.

• The IgnoreErrorsIntegration integration was removed. Use the ignore_exceptions option instead.
  Previously, both Symfony\Component\ErrorHandler\Error\FatalError and Symfony\Component\Debug\Exception\FatalErrorException were ignored by default.
  To continue ignoring these exceptions, make the following changes to the config file:

  // config/packages/sentry.yaml
  
  sentry:
    options:
      ignore_exceptions:
        - 'Symfony\Component\ErrorHandler\Error\FatalError'
        - 'Symfony\Component\Debug\Exception\FatalErrorException'

  This option performs an is_a check now, so you can also ignore more generic exceptions.

Features

• Add support for Sentry Developer Metrics (#​1619)

  use function Sentry\metrics;
  
  // Add 4 to a counter named hits
  metrics()->increment(key: 'hits', value: 4);
  
  // Add 25 to a distribution named response_time with unit milliseconds
  metrics()->distribution(key: 'response_time', value: 25, unit: MetricsUnit::millisecond());
  
  // Add 2 to gauge named parallel_requests, tagged with type: "a"
  metrics()->gauge(key: 'parallel_requests', value: 2, tags: ['type': 'a']);
  
  // Add a user's email to a set named users.sessions, tagged with role: "admin"
  metrics()->set('users.sessions', 'jane.doe@example.com', null, ['role' => User::admin()]);

  Metrics are automatically sent to Sentry at the end of a request, hooking into Symfony's kernel.terminate event.

• Add new fluent APIs (#​1601)

  // Before
  $transactionContext = new TransactionContext();
  $transactionContext->setName('GET /example');
  $transactionContext->setOp('http.server');
  
  // After
  $transactionContext = (new TransactionContext())
      ->setName('GET /example');
      ->setOp('http.server');

• Simplify the breadcrumb API (#​1603)

  // Before
  \Sentry\addBreadcrumb(
      new \Sentry\Breadcrumb(
          \Sentry\Breadcrumb::LEVEL_INFO,
          \Sentry\Breadcrumb::TYPE_DEFAULT,
          'auth',                // category
          'User authenticated',  // message (optional)
          ['user_id' => $userId] // data (optional)
      )
  );
  
  // After
  \Sentry\addBreadcrumb(
      category: 'auth',
      message: 'User authenticated', // optional
      metadata: ['user_id' => $userId], // optional
      level: Breadcrumb::LEVEL_INFO, // set by default
      type: Breadcrumb::TYPE_DEFAULT, // set by default
  );

• New default cURL HTTP client (#​1589)

  The SDK now ships with its own HTTP client based on cURL. A few new options were added.

  // config/packages/sentry.yaml
  
  sentry:
    options:
      - http_proxy_authentication: 'username:password' // user name and password to use for proxy authentication
      - http_ssl_verify_peer: false // default true, verify the peer's SSL certificate
      - http_compression: false // default true, http request body compression

  To use a different client, you may use the http_client option.
  To use a different transport, you may use the transport option. A custom transport must implement the TransportInterface.
  If you use the transport option, the http_client option has no effect.

Misc

• The abandoned package php-http/message-factory was removed.

v4.14.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.14.0.

Features

• Add support for doctrine/dbal: ^4.0 (#​811)

Bug Fixes

• Fix overwritting DbalTracingPass (#​808)
• Use AbstractDriverMiddleware (#​810)

v4.13.2

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.13.2.

Bug Fixes

• Fix detection of the installed version of symfony/http-client (#​797)

v4.13.1

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.13.1.

Bug Fixes

• Fix the HTTP client decoration when no http_client service is registered (#​792)

v4.13.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.13.0.

Features

• Add support for Symfony 7 (#​761)

Bug Fixes

• Fix the decoration of the HTTP client when tracing is enabled (#​786)

v4.12.0

Compare Source

Features

• Add support for symfony/psr-http-message-bridge: ^6.4 (#​750)
• Report individual exceptions from DelayedMessageHandlingException (#​760)

v4.11.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.11.0.

Bug Fixes

• Silence TokenInterface::isAuthenticated deprecation in LoginListener (#​755)

Misc

• Prefer the SENTRY_RELEASE environment variable over the package root version (#​753)

v4.10.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.10.0.

Features

• Tracing without Performance (#​742)

  The SDK will now continue a trace from incoming HTTP requests, even if performance is not enabled.
  To continue a trace outward, you may attach the Sentry tracing headers to any HTTP client request.
  You can fetch the required header values by calling \Sentry\getBaggage() and \Sentry\getTraceparent().

• Add ignore_exceptions and ignore_transactions options (#​724)

Misc

• Improve setting logged-in users on the scope (#​720)
• Move DB span tags to span data (#​743)
• Set the span status when tracing an HTTP client request (#​748)

v4.9.2

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.2.

Bug Fixes

• We decided to revert two previous PRs that aimed to remove deprecation warnings during test runs (#​736)

  • Revert: Add a new Doctrine DBAL tracing driver that does not implement the deprecated VersionAwarePlatformDriver (#​723)
  • Revert: Fix a regression in TracingDriverForV32 by adding VersionAwarePlatformDriver::createDatabasePlatformForVersion (#​731)

We are sorry for the inconvenience caused by these changes.

v4.9.1

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.1.

Bug Fixes

• Fix a regression in TracingDriverForV32 by adding VersionAwarePlatformDriver::createDatabasePlatformForVersion (#​731)

v4.9.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.0.

Features

• Add a new Doctrine DBAL tracing driver that does not implement the deprecated VersionAwarePlatformDriver (#​723)

  The driver is automatically picked if doctrine/dbal version 3.2.0 or higher is installed.

Bug Fixes

• Fix config type of http_connect_timeoutand http_timeout options (#​721)

Misc

• Bump the underlying PHP SDK to version ^3.19 (#​725)

v4.8.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.8.0.

Features

• Set cache keys as span descriptions (#​677)

  To better identify the source of a cache operation, we now set the cache key as the description of cache op spans.

Bug Fixes

• Add direct dependency for guzzlehttp/psr7 (#​708)
• Drop kernel.build_dir param below Symfony 5.2 (#​711)

v4.7.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.7.0.

Features

• Add profiles_sample_rate config option (#​698)

  With this new config option, you can now use our new profiling feature in Symfony as well.
  Please consult https://github.com/getsentry/sentry-php/releases/3.15.0 for setup instructions.

v4.6.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.6.0.
This release contains a colorful bouquet of new features.

Features

• Report exceptions to Sentry as unhandled by default (#​674)

  All unhandled exceptions will now be marked as handled: false. You can query for such events on the issues list page,
  by searching for error.handled:false.

• Exceptions from messages which will be retried are sent to Sentry as handled (#​674)

  All unhandled exceptions happening on the message bus will now be unpacked and reported individually.
  The WorkerMessageFailedEvent::willRetry property is used to determine the handled value of the event sent to Sentry.

• Add register_error_handler config option (#​687)

  With this option, you can disable the global error and exception handlers of the base PHP SDK.
  If disabled, only events logged by Monolog will be sent to Sentry.

    sentry:
        dsn: '%env(SENTRY_DSN)%'
        register_error_listener: false
        register_error_handler: false
  
    monolog:
        handlers:
            sentry:
                type: sentry
                level: !php/const Monolog\Logger::ERROR
                hub_id: Sentry\State\HubInterface

• Add before_send_transaction (#​691)

  Similar to before_send, you can now apply additional logic for transaction events.
  You can mutate the transaction event before it is sent to Sentry. If your callback returns null,
  the event is dropped.

    sentry:
        options:
            before_send_transaction: 'sentry.callback.before_send_transaction'
  
    services:
        sentry.callback.before_send_transaction:
            class: 'App\Service\Sentry'
            factory: [ '@​App\Service\Sentry', 'getBeforeSendTransaction' ]

    <?php
  
    namespace App\Service;
  
    class Sentry
    {
        public function getBeforeSendTransaction(): callable
        {
            return function (\Sentry\Event $event): ?\Sentry\Event {
                return $event;
            };
        }
    }

• Use the _route attribute as the transaction name (#​692)

  If you're using named routes, the SDK will default to use this attribute as the transaction name.
  With this change, you should be able to see a full list of your transactions on the performance page,
  instead of << unparameterized >>.

  You may need to update your starred transactions as well as your dashboards due to this change.

Bug Fixes

• Sanatize HTTP client spans (#​690)

v4.5.0

Compare Source

• Symfony version 3.4 is no longer supported
  • Drop Symfony support below 4.4 (#​643)
• feat: Add support for tracing of Symfony HTTP client requests (#​606)
  • feat: Add support for HTTP client baggage propagation (#​663)
  • ref: Add proper HTTP client span descriptions (#​680)
• feat: Support logging the impersonator user, if any (#​647)
• ref: Use a constant for the SDK version (#​662)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: composer update sentry/sentry-symfony:5.1.0 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Dependency symfony/symfony is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires sentry/sentry-symfony ^5.0 -> satisfiable by sentry/sentry-symfony[5.1.0].
    - sentry/sentry-symfony 5.1.0 requires symfony/config ^4.4.20||^5.0.11||^6.0||^7.0 -> found symfony/config[v4.4.20, ..., v4.4.44, v5.0.11, ..., v5.4.46, v6.0.0, ..., v6.4.14, v7.0.0, ..., v7.2.3] but these were not loaded, likely because it conflicts with another require.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.