Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update backendDependencies (major) #513

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nunomaduro/collision ^7.0 -> ^8.0 age adoption passing confidence
sentry/sentry-laravel (source) ^3.7 -> ^4.0 age adoption passing confidence

Release Notes

nunomaduro/collision (nunomaduro/collision)

v8.1.0

Compare Source

Added
  • Laravel v11 support
  • PHPUnit v11 support
  • Pest v3 support

v8.0.1

Compare Source

v8.0.0

Compare Source

Added
  • Symfony v7 support
Removed
  • Symfony v6 support
getsentry/sentry-laravel (sentry/sentry-laravel)

v4.1.2

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.1.2.

Bug Fixes
  • Fix unable to set callable for integrations option (#​826)

  • Fix performance traces not being collected for Laravel Lumen unless missing routes are reported (#​822)

  • Fix configuration options for queue job tracing not applying correctly (#​820)

Misc
  • Allow newer versions of symfony/psr-http-message-bridge dependency (#​829)

v4.1.1

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.1.1.

Bug Fixes
  • Fix missing sentryMonitor() macro when command is called outside the CLI environment (#​812)

  • Don't call terminating() in Lumen apps below 9.1.4 (#​815)

v4.1.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.1.0.

Features
  • Capture SQL query bindings (parameters) in SQL query spans (#​804)

    To enable this feature, update your config/sentry.php file or set the SENTRY_TRACE_SQL_BINDINGS_ENABLED environment variable to true.

    'tracing' => [
        'sql_bindings' => true,
    ],
Misc
  • Unify backtrace origin span attributes (#​803)
  • Add ignore_exceptions & ignore_transactions to default config (#​802)

v4.0.0

Compare Source

The Sentry SDK team is thrilled to announce the immediate availability of Sentry Laravel SDK v4.0.0.

Breaking Change

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.

    // config/sentry.php
    
    'ignore_exceptions' => [BadThingsHappenedException::class],

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

Features
  • Enable distributed tracing for outgoing HTTP client requests (#​797)

    This feature is only available on Laravel >= 10.14.
    When making a request using the Laravel Http facade, we automatically attach the sentry-trace and baggage headers.

    This behaviour can be controlled by setting trace_propagation_targets in your config/sentry.php file.

    // config/sentry.php
    
    // All requests will contain the tracing headers. This is the default behaviour.
    'trace_propagation_targets' => null,
    
    // To turn this feature off completely, set the option to an empty array.
    'trace_propagation_targets' => [],
    
    // To only attach these headers to some requests, you can allow-list certain hosts.
    'trace_propagation_targets' => [
        'examlpe.com',
        'api.examlpe.com',
    ],

    Please make sure to remove any custom code that injected these headers previously.
    If you are using the Sentry\Tracing\GuzzleTracingMiddleware provided by our underlying PHP SDK, you must also remove it.

  • Add support for Laravel Livewire 3 (#​798)

    The SDK now creates traces and breadcrumbs for Livewire 3 as well.
    Both the class-based and Volt usage are supported.

    // config/sentry.php
    
    'breadcrumbs' => [
        // Capture Livewire components in breadcrumbs
        'livewire' => true,
    ],
    'tracing' => [
        // Capture Livewire components as spans
        'livewire' => true,
    ],
  • Add new fluent APIs (#​1601)

    // Before
    $spanContext = new SpanContext();
    $spanContext->setDescription('myFunction');
    $spanContext->setOp('function');
    
    // After
    $spanContext = (new SpanContext())
        ->setDescription('myFunction');
        ->setOp('function');
  • 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)

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

Configuration

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Jan 17, 2024

⚠ 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: backend/composer.lock
Command failed: composer update nunomaduro/collision:8.1.0 sentry/sentry-laravel:4.1.2 --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 laravel/framework 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 nunomaduro/collision ^8.0 -> satisfiable by nunomaduro/collision[v8.1.0].
    - nunomaduro/collision v8.1.0 requires nunomaduro/termwind ^2.0.0 -> found nunomaduro/termwind[v2.0.0, 2.x-dev] 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant