-
Notifications
You must be signed in to change notification settings - Fork 2
chore: Regenerate package-lock.json files for Next.js 15.5.7 #539
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
Conversation
|
Co-authored-by: colinmurphy <682403+colinmurphy@users.noreply.github.com>
Co-authored-by: colinmurphy <682403+colinmurphy@users.noreply.github.com>
Co-authored-by: colinmurphy <682403+colinmurphy@users.noreply.github.com>
📦 Plugin Artifacts Ready!Download from GitHub Actions run Available plugins:
See the "Artifacts" section at the bottom of the Actions run page |
Description
PR #538 updated
package.jsonfiles to Next.js 15.5.7 but did not regeneratepackage-lock.jsonfiles, leaving installations vulnerable to GHSA-9qr9-h5gf-34mp.Changed:
package-lock.jsonfiles (were locked at 15.4.7 or 15.5.2)^15.5→^15.5.7) and regenerated its lockfile (was at 15.5.5)Files updated:
examples/next/*/example-app/package-lock.json(4 files)packages/toolbar/examples/next/example-app/package.json+package-lock.jsonplugins/hwp-previews/examples/hwp-preview-rest/example-app/package-lock.jsonplugins/wpgraphql-webhooks/examples/webhooks-isr/example-app/package-lock.jsonAll tracked lockfiles now reference Next.js 15.5.7. Security audits confirm 0 vulnerabilities.
Related Issue
Completes work from #538
Dependant PRs
None
Type of Change
How Has This Been Tested?
npm auditon updated examples (0 vulnerabilities)Screenshots
N/A
Checklist
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.