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

deps(deps): update dependency sentry/sentry-laravel to v4.7.1 #427

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 18, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry/sentry-laravel (source) 4.6.0 -> 4.7.1 age adoption passing confidence

Release Notes

getsentry/sentry-laravel (sentry/sentry-laravel)

v4.7.1

Compare Source

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

Bug Fixes
  • Always remove the XSRF-TOKEN cookie value before sending to Sentry (#​920)
  • Fix trace durations when using Octane (#​921)
  • Handle clousre route names (#​921)
  • Don't rely on facades when accessing the Laravel context (#​922)
  • Normalize array of cache key names before converting to string (#​923)

v4.7.0

Compare Source

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

Features
  • Add support for Cache Insights Module (#​914). To learn more about this module, visit https://docs.sentry.io/product/insights/caches/. This feature requires Laravel v11.11.0 or higher.

    Cache tracing is enabled by default for new SDK installations. To enable this feature in your existing installation, update your config/sentry.php file with 'cache' => env('SENTRY_TRACE_CACHE_ENABLED', true), under 'tracing'.

v4.6.1

Compare Source

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

Bug Fixes
  • Fix wrong queue grouping in the queue Insights Module (#​910)

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.

🔕 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 renovate bot requested a review from lotyp as a code owner June 18, 2024 17:01
@renovate renovate bot enabled auto-merge (rebase) June 18, 2024 17:01
Copy link

codecov bot commented Jun 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.46%. Comparing base (bf33177) to head (8b7366d).

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #427   +/-   ##
==========================================
  Coverage      54.46%   54.46%           
  Complexity        43       43           
==========================================
  Files             22       22           
  Lines            112      112           
==========================================
  Hits              61       61           
  Misses            51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot changed the title deps(deps): update dependency sentry/sentry-laravel to v4.6.1 deps(deps): update dependency sentry/sentry-laravel to v4.7.0 Jul 11, 2024
@renovate renovate bot force-pushed the renovate/sentry-sentry-laravel-4.x-lockfile branch from c76e1c6 to bdeb1c4 Compare July 11, 2024 10:43
@renovate renovate bot force-pushed the renovate/sentry-sentry-laravel-4.x-lockfile branch from bdeb1c4 to 8b7366d Compare July 17, 2024 17:58
@renovate renovate bot changed the title deps(deps): update dependency sentry/sentry-laravel to v4.7.0 deps(deps): update dependency sentry/sentry-laravel to v4.7.1 Jul 17, 2024
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

0 participants