Skip to content

[Snyk] Upgrade package-lock from 1.0.3 to 1.0.5 - #2

Open
Snapp949 wants to merge 1 commit into
masterfrom
snyk-upgrade-fbf3cd5b3287500dca170c8206bfd189
Open

[Snyk] Upgrade package-lock from 1.0.3 to 1.0.5#2
Snapp949 wants to merge 1 commit into
masterfrom
snyk-upgrade-fbf3cd5b3287500dca170c8206bfd189

Conversation

@Snapp949

@Snapp949 Snapp949 commented Jul 15, 2025

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade package-lock from 1.0.3 to 1.0.5.

ℹ️ 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 5 years ago.

Release notes
Package name: package-lock from package-lock 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:

Summary by Sourcery

Upgrade package-lock dependency and lockfile from version 1.0.3 to 1.0.5

Enhancements:

  • Update package.json to bump package-lock to ^1.0.5
  • Regenerate package-lock.json to reflect the new dependency version

Snyk has created this PR to upgrade package-lock from 1.0.3 to 1.0.5.

See this package in npm:
package-lock

See this project in Snyk:
https://app.snyk.io/org/snapp949/project/b62f72c3-e17a-40bc-ae9f-11b336583a64?utm_source=github&utm_medium=referral&page=upgrade-pr
@sourcery-ai

sourcery-ai Bot commented Jul 15, 2025

Copy link
Copy Markdown

Reviewer's Guide

This PR upgrades the package-lock dependency from 1.0.3 to 1.0.5 by updating the version in package.json and regenerating the lock file accordingly.

File-Level Changes

Change Details Files
Upgrade package-lock dependency to version 1.0.5
  • Update version specifier in package.json from ^1.0.3 to ^1.0.5
  • Regenerate package-lock.json to reflect the updated dependency
package.json
package-lock.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

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.

2 participants