Skip to content

Conversation

@nishanthmahasamudram
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade body-parser from 1.20.3 to 2.0.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 3 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: body-parser from body-parser GitHub release notes

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:

Snyk has created this PR to upgrade body-parser from 1.20.3 to 2.0.0.

See this package in npm:
body-parser

See this project in Snyk:
https://app.snyk.io/org/digital-prison-services/project/3233b79d-1451-467e-8dcd-bd2549215692?utm_source=github&utm_medium=referral&page=upgrade-pr
@nishanthmahasamudram nishanthmahasamudram requested a review from a team as a code owner October 1, 2024 09:54
…to v2 when that is still tagged “next” (not “latest”) on npmjs.com
@ushkarev
Copy link
Contributor

ushkarev commented Oct 1, 2024

it’s weird that snyk wants body-parser to go to v2 when that is still tagged “next” (not “latest”) on npmjs.com

@ushkarev ushkarev merged commit 42e83c2 into main Oct 1, 2024
7 checks passed
@ushkarev ushkarev deleted the snyk-upgrade-984c7f0648df3eba72b3276e301144d5 branch October 1, 2024 10:35
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.

3 participants