Repository navigation
Update dev dependencies to clear the critical Dependabot alerts - #5
Merged
Merged
Conversation
Combines the open Dependabot PRs (#1, #2, #3) into one change, since they all rewrite package-lock.json and would conflict with each other once one merged. Every package touched is a devDependency or comes only through one. The plugin has no runtime dependencies, and its peer ranges are unchanged, so installs of the published package are unaffected and no release is needed. Tested locally on Node 26: typecheck, vitest, build, and the CI-mode leak check pass, and npm audit shows no critical or high advisories. Not tested against a real Payload app. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Combines the open Dependabot PRs (#1, #2, #3) into one change, since they all
rewrite package-lock.json and would conflict with each other once one merged.
Every package touched is a devDependency or comes only through one. The
plugin has no runtime dependencies, and its peer ranges are unchanged, so
installs of the published package are unaffected and no release is needed.
Tested locally on Node 26: typecheck, vitest, build, and the CI-mode leak
check pass, and npm audit shows no critical or high advisories. Not tested
against a real Payload app.
The Dependabot PRs should close on their own once this merges, because their updates are then already on main.
🤖 Generated with Claude Code