Repository navigation
meta: update brace-expansion - #151
dcavalcante wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
|
Thanks @dcavalcante but we handle dependency updates via Dependabot. So these should/will be picked up by it eventually. We tend to not accept package update PRs for security reasons 🙇 |
no worries @ovflowd! it just popped up while I was working on the repo, so I sent it along.. |
Description
Updates the transitive
brace-expansionversions inpackage-lock.jsonto resolve vulnerabilities reported bynpm audit.No direct dependencies or dependency ranges are changed. The existing ranges already allow the patched versions, so this is a lockfile-only update.
Updated versions:
brace-expansion5.0.9→5.0.12brace-expansion2.1.4→2.1.7The affected entries are pulled in through
minimatch,glob, and@npmcli/map-workspaces.npm audit
Before the update,
npm auditreported:Original npm audit output
After updating the lockfile:
Validation
Verified locally with:
npm auditreports no vulnerabilities and all 20 end-to-end tests pass.