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 express from 4.18.1 to 4.18.2 #16

Merged
merged 1 commit into from
Apr 1, 2023

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Apr 1, 2023

Snyk has created this PR to upgrade express from 4.18.1 to 4.18.2.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 6 months ago, on 2022-10-08.
Release notes
Package name: express
  • 4.18.2 - 2022-10-08
    • Fix regression routing a large stack in a single route
    • deps: body-parser@1.20.1
      • deps: qs@6.11.0
      • perf: remove unnecessary object clone
    • deps: qs@6.11.0
  • 4.18.1 - 2022-04-29
    • Fix hanging on large stack of sync routes
from express GitHub release notes
Commit messages
Package name: express

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@Say383 Say383 force-pushed the snyk-upgrade-a79ee6350ae7eeef3cf3308aec2d1487 branch from 141d60c to ce9b951 Compare April 1, 2023 19:31
@Say383 Say383 merged commit c1fc5cc into v1 Apr 1, 2023
@Say383 Say383 deleted the snyk-upgrade-a79ee6350ae7eeef3cf3308aec2d1487 branch April 10, 2023 20:13
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