Bump path-to-regexp
, express
, nanoid
#2365
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Fixes GHSA-rhx6-c78j-4q9w:
Bumps
express
(an indirect peer dependency) from4.21.0
to4.21.2
. This in-turns bumpspath-to-regexp
from0.1.10
to0.1.12
to fix the advisory.Fixes GHSA-mwcw-c2x4-8c55:
Bumps
nanoid@<3.3.8
to3.3.8
andnanoid@>=4.0.0 <5.0.9
to>=5.0.9
. Closes #2366 in favor of this PR since that PR didn't fix the advisory completely (run).Testing
Docs
According to
pnpm why express
andpnpm why path-to-regexp
,express
andpath-to-regexp
were only used in a dep workspace (e2e
).pnpm why outputs
pnpm why express
pnpm why path-to-regexp
According to
pnpm why nanoid
, it is also only used in a dev workspace:pnpm why output
Thus, no changeset added. But I'm not quite sure if
pnpm why
's outputs were exhaustive.