Skip to content

Conversation

@snyk-io
Copy link
Contributor

@snyk-io snyk-io bot commented Jun 5, 2025

snyk-io[bot] Contributor Powered by Pull Request Badge

snyk-top-banner

Snyk has created this PR to upgrade @sentry/browser from 9.17.0 to 9.19.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: @sentry/browser
  • 9.19.0 - 2025-05-14
    • feat(react-router): Add otel instrumentation for server requests (#16147)
    • feat(remix): Vendor in opentelemetry-instrumentation-remix (#16145)
    • fix(browser): Ensure spans auto-ended for navigations have cancelled reason (#16277)
    • fix(node): Pin @ fastify/otel fork to direct url to allow installing without git (#16287)
    • fix(react): Handle nested parameterized routes in reactrouterv3 transaction normalization (#16274)

    Work in this release was contributed by @ sidx1024. Thank you for your contribution!

    Bundle size 📦

    Path Size
    @ sentry/browser 23.4 KB
    @ sentry/browser - with treeshaking flags 23.06 KB
    @ sentry/browser (incl. Tracing) 37.31 KB
    @ sentry/browser (incl. Tracing, Replay) 74.53 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 67.72 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 79.19 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 91 KB
    @ sentry/browser (incl. Feedback) 39.8 KB
    @ sentry/browser (incl. sendFeedback) 28.03 KB
    @ sentry/browser (incl. FeedbackAsync) 32.79 KB
    @ sentry/react 25.17 KB
    @ sentry/react (incl. Tracing) 39.27 KB
    @ sentry/vue 27.67 KB
    @ sentry/vue (incl. Tracing) 39.07 KB
    @ sentry/svelte 23.43 KB
    CDN Bundle 24.58 KB
    CDN Bundle (incl. Tracing) 37.33 KB
    CDN Bundle (incl. Tracing, Replay) 72.37 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 77.68 KB
    CDN Bundle - uncompressed 71.72 KB
    CDN Bundle (incl. Tracing) - uncompressed 110.5 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 221.78 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 234.31 KB
    @ sentry/nextjs (client) 40.88 KB
    @ sentry/sveltekit (client) 37.77 KB
    @ sentry/node 154.29 KB
    @ sentry/node - without tracing 95.6 KB
    @ sentry/aws-serverless 120.36 KB
  • 9.18.0 - 2025-05-13

    Important changes

    • feat: Support Node 24 (#16236)

    We now also publish profiling binaries for Node 24.

    Other changes

    • deps(node): Bump import-in-the-middle to 1.13.1 (#16260)
    • feat: Export consoleLoggingIntegration from vercel edge sdk (#16228)
    • feat(cloudflare): Add support for email, queue, and tail handler (#16233)
    • feat(cloudflare): Improve http span data (#16232)
    • feat(nextjs): Add more attributes for generation functions (#16214)
    • feat(opentelemetry): Widen peer dependencies to support Otel v2 (#16246)
    • fix(core): Gracefully handle invalid baggage entries (#16257)
    • fix(node): Ensure traces are propagated without spans in Node 22+ (#16221)
    • fix(node): Use sentry forked @ fastify/otel dependency with pinned Otel v1 deps (#16256)
    • fix(remix): Remove vendored types (#16218)

    Bundle size 📦

    Path Size
    @ sentry/browser 23.4 KB
    @ sentry/browser - with treeshaking flags 23.22 KB
    @ sentry/browser (incl. Tracing) 37.3 KB
    @ sentry/browser (incl. Tracing, Replay) 74.53 KB
    @ sentry/browser (incl. Tracing, Replay) - with treeshaking flags 68.37 KB
    @ sentry/browser (incl. Tracing, Replay with Canvas) 79.18 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) 90.99 KB
    @ sentry/browser (incl. Feedback) 39.8 KB
    @ sentry/browser (incl. sendFeedback) 28.03 KB
    @ sentry/browser (incl. FeedbackAsync) 32.79 KB
    @ sentry/react 25.17 KB
    @ sentry/react (incl. Tracing) 39.26 KB
    @ sentry/vue 27.67 KB
    @ sentry/vue (incl. Tracing) 39.06 KB
    @ sentry/svelte 23.43 KB
    CDN Bundle 24.58 KB
    CDN Bundle (incl. Tracing) 37.33 KB
    CDN Bundle (incl. Tracing, Replay) 72.37 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) 77.67 KB
    CDN Bundle - uncompressed 71.72 KB
    CDN Bundle (incl. Tracing) - uncompressed 110.46 KB
    CDN Bundle (incl. Tracing, Replay) - uncompressed 221.75 KB
    CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 234.27 KB
    @ sentry/nextjs (client) 40.88 KB
    @ sentry/sveltekit (client) 37.76 KB
    @ sentry/node 155.42 KB
    @ sentry/node - without tracing 96 KB
    @ sentry/aws-serverless 121.5 KB
  • 9.17.0 - 2025-05-08
from @sentry/browser GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Podsumowanie wygenerowane przez Sourcery

Build:

  • Zaktualizowano wersję @sentry/browser w pliku package.json z 9.17.0 do 9.19.0
Original summary in English

Summary by Sourcery

Build:

  • Bump @sentry/browser version in package.json from 9.17.0 to 9.19.0

Snyk has created this PR to upgrade @sentry/browser from 9.17.0 to 9.19.0.

See this package in npm:
@sentry/browser

See this project in Snyk:
https://app.snyk.io/org/reisene/project/55e114f8-489e-4f14-b900-20574b041e59?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
@aviator-app
Copy link
Contributor

aviator-app bot commented Jun 5, 2025

Aviator Changeset actions:

@aviator-app
Copy link
Contributor

aviator-app bot commented Jun 5, 2025

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@semanticdiff-com
Copy link

semanticdiff-com bot commented Jun 5, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  package-lock.json  68% smaller
  package.json  0% smaller

@naming-conventions-bot
Copy link

Please follow naming conventions! 😿

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 5, 2025

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 5, 2025

Przewodnik Recenzenta

Zaktualizuj zależność @sentry/browser z wersji 9.17.0 do 9.19.0, dostosowując specyfikator wersji w package.json, aby uwzględnić najnowsze, niepowodujące konfliktów ulepszenia funkcji i poprawki błędów.

Zmiany na Poziomie Pliku

Zmiana Szczegóły Pliki
Aktualizacja wersji zależności @sentry/browser
  • Zmodyfikuj ciąg wersji w package.json z ^9.17.0 na ^9.19.0
package.json

Porady i polecenia

Interakcja z Sourcery

  • Uruchom nową recenzję: Skomentuj @sourcery-ai review w żądaniu pull request.
  • Kontynuuj dyskusje: Odpowiadaj bezpośrednio na komentarze recenzji Sourcery.
  • Wygeneruj zgłoszenie GitHub z komentarza recenzji: Poproś Sourcery o utworzenie
    zgłoszenia z komentarza recenzji, odpowiadając na niego. Możesz również odpowiedzieć na
    komentarz recenzji za pomocą @sourcery-ai issue, aby utworzyć z niego zgłoszenie.
  • Wygeneruj tytuł żądania pull request: Napisz @sourcery-ai w dowolnym miejscu w tytule
    żądania pull request, aby wygenerować tytuł w dowolnym momencie. Możesz również skomentować
    @sourcery-ai title w żądaniu pull request, aby (ponownie) wygenerować tytuł w dowolnym momencie.
  • Wygeneruj podsumowanie żądania pull request: Napisz @sourcery-ai summary w dowolnym miejscu
    w treści żądania pull request, aby wygenerować podsumowanie PR w dowolnym momencie, dokładnie tam, gdzie
    chcesz. Możesz również skomentować @sourcery-ai summary w żądaniu pull request, aby
    (ponownie) wygenerować podsumowanie w dowolnym momencie.
  • Wygeneruj przewodnik recenzenta: Skomentuj @sourcery-ai guide w żądaniu pull
    request, aby (ponownie) wygenerować przewodnik recenzenta w dowolnym momencie.
  • Rozwiąż wszystkie komentarze Sourcery: Skomentuj @sourcery-ai resolve w żądaniu
    pull request, aby rozwiązać wszystkie komentarze Sourcery. Przydatne, jeśli już
    odniosłeś się do wszystkich komentarzy i nie chcesz ich więcej widzieć.
  • Odrzuć wszystkie recenzje Sourcery: Skomentuj @sourcery-ai dismiss w żądaniu
    pull request, aby odrzucić wszystkie istniejące recenzje Sourcery. Szczególnie przydatne, jeśli
    chcesz zacząć od nowa z nową recenzją - nie zapomnij skomentować
    @sourcery-ai review, aby uruchomić nową recenzję!

Dostosowywanie Doświadczenia

Uzyskaj dostęp do swojego panelu, aby:

  • Włączyć lub wyłączyć funkcje recenzji, takie jak podsumowanie żądania pull request
    wygenerowane przez Sourcery, przewodnik recenzenta i inne.
  • Zmienić język recenzji.
  • Dodawać, usuwać lub edytować niestandardowe instrukcje recenzji.
  • Dostosować inne ustawienia recenzji.

Uzyskiwanie Pomocy

Original review guide in English

Reviewer's Guide

Update the @sentry/browser dependency from version 9.17.0 to 9.19.0 by adjusting the version specifier in package.json to incorporate the latest non-breaking feature enhancements and bug fixes.

File-Level Changes

Change Details Files
Bump @sentry/browser dependency version
  • Modify version string in package.json from ^9.17.0 to ^9.19.0
package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@deepsource-io
Copy link
Contributor

deepsource-io bot commented Jun 5, 2025

Here's the code health analysis summary for commits f0db307..eb8574d. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗
DeepSource PHP LogoPHP✅ SuccessView Check ↗
DeepSource Test coverage LogoTest coverage⚠️ Artifact not reportedTimed out: Artifact was never reportedView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

@mergify
Copy link
Contributor

mergify bot commented Jun 5, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Do not merge outdated PRs

Wonderful, this rule succeeded.

Make sure PRs are almost up to date before merging

  • #commits-behind <= 10

@github-actions
Copy link

github-actions bot commented Jun 5, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/@sentry-internal/browser-utils 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry-internal/feedback 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry-internal/replay 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry-internal/replay-canvas 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry/browser 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry/core 9.26.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected
npm/@sentry/browser ^9.19.0 🟢 5.2
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Fuzzing⚠️ 0project is not fuzzed
SAST🟢 7SAST tool detected but not run on all commits
Vulnerabilities⚠️ 075 existing vulnerabilities detected

Scanned Files

  • package-lock.json
  • package.json

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@reisene
Copy link
Owner

reisene commented Jun 5, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

@snyk-io
Copy link
Contributor Author

snyk-io bot commented Jun 5, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 9, 2025

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@mergify mergify bot merged commit f701d70 into main Jun 9, 2025
27 of 45 checks passed
@mergify mergify bot deleted the snyk-upgrade-7482df7466dd5f20e95bda4f87ad26ad branch June 9, 2025 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants