Skip to content
This repository has been archived by the owner on May 9, 2024. It is now read-only.

Bump sentry/sentry-laravel from 3.3.3 to 3.4.0 #685

Merged
merged 1 commit into from
May 10, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 8, 2023

Bumps sentry/sentry-laravel from 3.3.3 to 3.4.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

3.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.4.0.

Features

  • Add helper to report lazy loading violations [(#678)](getsentry/sentry-laravel#678)

    We've added a new helper that makes reporting lazy loading violation to Sentry in production very easy:

    // See: https://laravel.com/docs/10.x/eloquent-relationships#preventing-lazy-loading
    \Illuminate\Database\Eloquent\Model::preventLazyLoading();
    // In production we just report the lazy loading violation instead of crashing the application since it's a performance issue not a security issue
    if (app()->isProduction()) {
    \Illuminate\Database\Eloquent\Model::handleLazyLoadingViolationUsing(
    \Sentry\Laravel\Integration::lazyLoadingViolationReporter(),
    );
    }

    We let you know which model and relation caused the lazy loading violation and we also include the origin of the violation so you can find the culprit quickly.

  • Reintroduce Laravel Lumen support [(#685)](getsentry/sentry-laravel#685)

    We dropped support for Laravel Lumen (10.x) in v3.0.0, but we are happy to announce that it is back!

Changelog

Sourced from sentry/sentry-laravel's changelog.

3.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.4.0.

Features

  • Add helper to report lazy loading violations [(#678)](getsentry/sentry-laravel#678)

    We've added a new helper that makes reporting lazy loading violation to Sentry in production very easy:

    // See: https://laravel.com/docs/10.x/eloquent-relationships#preventing-lazy-loading
    \Illuminate\Database\Eloquent\Model::preventLazyLoading();
    // In production we just report the lazy loading violation instead of crashing the application since it's a performance issue not a security issue
    if (app()->isProduction()) {
    \Illuminate\Database\Eloquent\Model::handleLazyLoadingViolationUsing(
    \Sentry\Laravel\Integration::lazyLoadingViolationReporter(),
    );
    }

    We let you know which model and relation caused the lazy loading violation and we also include the origin of the violation so you can find the culprit quickly.

  • Reintroduce Laravel Lumen support [(#685)](getsentry/sentry-laravel#685)

    We dropped support for Laravel Lumen (10.x) in v3.0.0, but we are happy to announce that it is back!

Commits

Dependabot compatibility score

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 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)

Bumps [sentry/sentry-laravel](https://github.com/getsentry/sentry-laravel) from 3.3.3 to 3.4.0.
- [Release notes](https://github.com/getsentry/sentry-laravel/releases)
- [Changelog](https://github.com/getsentry/sentry-laravel/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-laravel@3.3.3...3.4.0)

---
updated-dependencies:
- dependency-name: sentry/sentry-laravel
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 8, 2023
@codecov
Copy link

codecov bot commented May 8, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (8c5790d) 8.65% compared to head (3bbe97e) 8.65%.

Additional details and impacted files
@@           Coverage Diff           @@
##              main    #685   +/-   ##
=======================================
  Coverage     8.65%   8.65%           
  Complexity      58      58           
=======================================
  Files           18      18           
  Lines          208     208           
=======================================
  Hits            18      18           
  Misses         190     190           
Flag Coverage Δ
unittests 8.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@gomzyakov gomzyakov merged commit c0b994d into main May 10, 2023
@gomzyakov gomzyakov deleted the dependabot/composer/sentry/sentry-laravel-3.4.0 branch May 10, 2023 09:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant