[dependabot]

Bumps the patch group with 1 update in the / directory: @cldmv/fix-headers.

Updates @cldmv/fix-headers from 2.2.1 to 2.2.2

Release notes

Sourced from @​cldmv/fix-headers's releases.

v2.2.2

@cldmv/fix-headers v2.2.2 Changelog

Release Date: October 2026 Release Type: Patch Branch: release/2.2.2

---

Overview

Version 2.2.2 is a dependency refresh. Everything that changed is in package-lock.json: the package.json ranges are untouched, and the only change to package.json is the version number. The source, dist/, bin/, the generated types and the declared dependency ranges are exactly as in v2.2.1.

One runtime dependency moved inside its existing range: ignore 7.0.10 → 7.0.12. It is the only dependency fix-headers declares (^7.0.5), and it is kept external by the build, so it is not bundled into dist/. A consumer's install already resolves ignore from that range, so a published 2.2.2 gets a current 7.0.x either way; the lockfile change affects this repository's own development and CI. The rest of the lockfile movement is development tooling, including a chalk major version and a Node.js 22 floor on the test runner's own tree (see Dependencies).

---

🔧 Dependencies

Every entry is a lockfile-only update within the existing package.json range. The ranges still read ignore ^7.0.5, @cldmv/vitest-runner ^1.4.2, vitest ^5.0.0 and eslint ^10.11.0, and so on.

Runtime

• ignore 7.0.10 → 7.0.12 (#138). Upstream's two patch releases drop a pattern that normalizes to nothing, and make trimming and unescaping of pattern whitespace run in linear time. They also fix handling of trailing spaces in directory patterns. The range allowed these versions before, and engines.node for the package (>=22.12.0) is unchanged.

Development

• @cldmv/vitest-runner 1.5.1 → 1.5.3 (#138). This is the change with the widest effect. Version 1.5.2 moved the runner's own dependency chalk from 5.6.2 to 6.0.1, and 1.5.3 raised its engines.node from >=20.19.0 to >=22.12.0. In this lockfile chalk therefore moves from 5.6.2 to 6.0.1, a major version that requires Node.js 22 or later. fix-headers already requires Node.js >=22.12.0, so nothing here is newly excluded. Version 1.5.3 also fixes the runner's CommonJS entry, which now throws a clear ERR_REQUIRE_ESM error on a Node.js without require(esm), and relicenses the runner under Apache-2.0.
• vitest 5.0.2 → 5.0.3 (#134), with @vitest/coverage-v8, @vitest/mocker and @vitest/spy at 5.0.3. vite 8.3.1 → 8.3.2, rolldown 1.2.11 → 1.2.12 (and its platform bindings) and @oxc-project/types 0.151.0 → 0.152.0 moved with them in the lockfile.
• eslint 10.11.0 → 10.12.0 (#135).
• globals 17.12.0 → 17.13.0 (#137).
• @cldmv/eslint-plugin-jsonv 1.0.13 → 1.0.15, @cldmv/jsonv 1.1.1 → 1.1.3 and @cldmv/prettier-plugin-jsonv 1.1.0 → 1.1.3 (#138). These are the lint and format plugins for .jsonv files. The releases between these versions update test expectations and CI; this repository has no .jsonv files.
• @types/node 26.6.3 → 26.6.4 (#138).
• why-is-node-running 3.2.2 → 3.2.1, a transitive dependency of vitest. vitest 5.0.3 depends on exactly 3.2.1 where 5.0.2 allowed ^3.2.1, so the lockfile steps back to that version; it is a development-only package.

📚 Documentation

• NEW: docs/changelog/v2/v2.2.2.md: this changelog.
• README What's New promoted to v2.2.2.

---

Upgrade notes

• No breaking changes and no change to the fixHeaders API, the CLI, the header format or the declared dependency ranges: drop-in for v2.2.1.
• The published package differs from 2.2.1 only in its version field. Installs resolve ignore from ^7.0.5 as before.
• Contributors need Node.js 22.12 or later, which was already the repository's floor. Node.js 20 cannot install the development toolchain: @cldmv/vitest-runner 1.5.3 and chalk 6 both require Node.js 22.

---

... (truncated)

Commits

• 22e52e3 release: v2.2.2 - bump the patch group across 1 directory with 6 updates
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[cldmv-bot]

Auto-approved by CLDMV-bot: patch bump from 2.2.1 to 2.2.2.