Skip to content

fix(deps): resolve Dependabot alerts in dev/build lockfiles - #16

Merged
soderlind merged 1 commit into
mainfrom
fix/dependabot-alerts
Aug 5, 2026
Merged

fix(deps): resolve Dependabot alerts in dev/build lockfiles#16
soderlind merged 1 commit into
mainfrom
fix/dependabot-alerts

Conversation

@soderlind

Copy link
Copy Markdown
Owner

Resolves all open Dependabot alerts via lockfile-only updates. No shipped code changes — every affected package is dev/build-only and excluded from the distributed plugin by .distignore.

npm (package-lock.json, via npm audit fix)

Package Now Alerts
undici 7.29.0 25, 26, 27, 28, 29
ip-address 10.4.0 23, 24, 36
fast-uri 3.1.5 35
postcss 8.5.25 34

composer (composer.lock)

Package Was → Now Alert
wp-coding-standards/wpcs 3.3.0 → 3.4.1 20 (arbitrary code execution)

Verification

  • npm run build — compiles
  • npm run test:js — 14 tests pass
  • composer run check — phpcs (WPCS 3.4.1) + phpstan clean, 44 phpunit tests

Not addressed

npm audit still lists 18 dev-only findings under @wordpress/scripts@33 (lighthouse → sentry → opentelemetry, brace-expansion). None are Dependabot alerts; they'd only clear with a breaking npm audit fix --force toolchain bump.

Refresh transitive npm packages (ip-address 10.4.0, fast-uri 3.1.5, undici
7.29.0, postcss 8.5.25) via `npm audit fix`, and upgrade
wp-coding-standards/wpcs 3.3.0 -> 3.4.1 (arbitrary code execution advisory).

All affected packages are dev/build-only and excluded from the distributed
plugin, so nothing that ships to users changes. Build, JS tests, and
composer check all pass.
@soderlind
soderlind merged commit 7147565 into main Aug 5, 2026
2 checks passed
@soderlind
soderlind deleted the fix/dependabot-alerts branch August 5, 2026 09:25
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.

1 participant