[vvillait88]

Summary

Bumps the dev dependency knip from 6.42.1 to 6.43.0 (published 2026-10-24, now past the 24h release-age soak). The lockfile change is knip plus its own oxc-parser 0.155.0 closure. Nothing shipped in the package changes.

Type of change

• Bug fix (no breaking change)
• New feature (no breaking change)
• Breaking change (existing callers must update)
• Docs, tests, or internal maintenance only

Public API

None. knip is a dev dependency only, so no release is needed.

Test plan

• bun install resolved knip 6.43.0.
• bun run knip passes on the new version.
• As a positive control, an unused file planted in node-sdk made knip 6.43.0 report it and exit 1.
• CI runs the full gate set.

Checklist

• Tests cover the new behavior, and the suite passes locally (no behavior change; CI runs the suite)
• Lint, format, and type checks pass (left to CI; the dev-tool bump does not touch source)
• Docs and README examples updated if the public surface changed (no public surface change)
• No secrets, credentials, or personal data in the diff or the tests

Worked with: Varun (dependency pass before the template release).

[vvillait88]

Review: no findings.

• Lock. bun.lock: the only moves are knip 6.42.1 to 6.43.0, oxc-parser 0.154.0 to 0.155.0 with its 19 @oxc-parser/binding-* packages, and the hoisted @oxc-project/types 0.154.0 to 0.155.0, which oxc-parser 0.155.0 asks for (^0.155.0). The one added entry (842 to 843 entries) is a nested rolldown/@oxc-project/types 0.154.0, which keeps rolldown on the exact =0.154.0 it pins, so rolldown's resolution is unchanged. No other package moved, and the only non-package lock lines are the workspace knip range. knip 6.43.0's own dependency list differs from 6.42.1's only in oxc-parser and unbash (a range that 6.0.x already satisfies), and its engines.node is unchanged (^20.19.0 || >=22.12.0).
• Manifests. package.json moves to ^6.43.0; it is the only manifest. No "knip" entry on 6.42.x remains in any package.json at the head.
• Config. The 6.43.0 release notes contain plugin additions, entry-file and resolver fixes, and --fix refinements, with no config-schema or rule change. The one change that can surface new findings is "follow npm lifecycle scripts and run-script aliases", which CI's knip step would catch.
• CI. All green, and ci runs bun run knip (plus node-compat 22, 24 and 26, Dependency Scan, and CodeQL).