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

[Snyk] Upgrade @sentry/vue from 7.119.2 to 8.42.0 #22

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

Conversation

gitworkflows
Copy link
Contributor

@gitworkflows gitworkflows commented Dec 25, 2024

snyk-top-banner

Snyk has created this PR to upgrade @sentry/vue from 7.119.2 to 8.42.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.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

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

  • The recommended version was released 23 days ago.


Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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:

Summary by Sourcery

Enhancements:

  • Upgrade the @sentry/vue package to version 8.42.0, which is 79 versions ahead of the current version.

Snyk has created this PR to upgrade @sentry/vue from 7.119.2 to 8.42.0.

See this package in yarn:
@sentry/vue

See this project in Snyk:
https://app.snyk.io/org/khulnasoft-devsecops/project/e7c74c0c-9f3f-4a96-84ac-eab678932db4?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Dec 25, 2024

Reviewer's Guide by Sourcery

This pull request upgrades the @sentry/vue package from version 7.119.2 to 8.42.0. This is a major version upgrade, so it has the potential to introduce breaking changes.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Upgrade @sentry/vue package
  • Updated the @sentry/vue package version in package.json
  • Regenerated yarn.lock to reflect the package version change
package.json
yarn.lock

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.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a 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. You can also use
    this command to specify where the summary should be inserted.

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

Copy link

coderabbitai bot commented Dec 25, 2024

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.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 docstrings to generate docstrings for this PR. (Beta)
  • @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.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

@gitworkflows
Copy link
Contributor Author

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

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

@NxPKG
Copy link
Contributor

NxPKG commented Dec 25, 2024

yarn.lock changes

Click to toggle table visibility
Name Status Previous Current
@babel/eslint-parser ADDED - 7.25.9
@nicolo-ribaudo/eslint-scope-5-internals ADDED - 5.1.1-v1
@sentry-internal/browser-utils ADDED - 8.47.0
@sentry-internal/feedback UPDATED 7.119.2 8.47.0
@sentry-internal/replay ADDED - 8.47.0
@sentry-internal/replay-canvas UPDATED 7.119.2 8.47.0
@sentry-internal/tracing DOWNGRADED 7.119.2 7.114.0
@sentry/browser UPDATED 7.119.2 8.47.0
@sentry/core UPDATED 7.119.2 8.47.0
@sentry/integrations REMOVED 7.119.2 -
@sentry/replay REMOVED 7.119.2 -
@sentry/types DOWNGRADED 7.119.2 7.114.0
@sentry/utils DOWNGRADED 7.119.2 7.114.0
@sentry/vue UPDATED 7.119.2 8.47.0
babel-eslint REMOVED 10.1.0 -
eslint-visitor-keys UPDATED 1.3.0 2.1.0
express-rate-limit ADDED - 7.5.0
immediate REMOVED 3.0.6 -
lie REMOVED 3.1.1 -
localforage REMOVED 1.10.0 -

Copy link

CI Failure Feedback 🧐

Action: build

Failed stage: Get Compressed Size [❌]

Failure summary:

The action failed during dependency installation because of a Node.js version incompatibility:

  • The package @achrinza/[email protected] requires Node.js version "8 || 10 || 12 || 14 || 16 || 17"
  • However, the environment is running Node.js v18.20.5
  • The yarn install command failed with exit code 1 due to this incompatibility

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    548:  Stripping hash from build chunks using '\\b\\w{8}\\.' pattern.
    549:  ##[group][current] Install Dependencies
    550:  Installing using yarn --frozen-lockfile
    551:  [command]/usr/local/bin/yarn --frozen-lockfile
    552:  yarn install v1.22.22
    553:  [1/5] Validating package.json...
    554:  [2/5] Resolving packages...
    555:  [3/5] Fetching packages...
    556:  error @achrinza/[email protected]: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.20.5"
    557:  error Found incompatible module.
    558:  info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
    559:  ##[error]The process '/usr/local/bin/yarn' failed with exit code 1
    

    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"
    

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    Copy link

    netlify bot commented Dec 25, 2024

    Deploy Preview for shipyard failed.

    Name Link
    🔨 Latest commit 44337b3
    🔍 Latest deploy log https://app.netlify.com/sites/shipyard/deploys/676bb1186aaa2c00080fa041

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

    Successfully merging this pull request may close these issues.

    3 participants