release: v0.0.12 - bump @cldmv/fix-headers to 2.1.4 and restamp file…

[cldmv-bot]

gitmulti v0.0.12 Changelog

Release Date: October 2026
Release Type: Patch
Branch: next → master

---

Overview

A dev-tooling dependency patch. The tools that maintain the comment headers at the top of the repository's source, test, config and workflow files move to their current releases: @cldmv/fix-headers from 2.1.1 to 2.2.0, and @cldmv/configs, the package that supplies the shared fix-headers configuration, from 1.2.0 to 1.2.4. No runtime code changed: gitmulti.js is exactly as in v0.0.11, and the runtime dependency (commander ^2.19.0) and its lockfile entry are unchanged.

The bumps were made with a header restamp in mind, but neither produced any header change in this repository: running npm run fix:headers against this release rewrites 0 files, so the only files touched are package.json and package-lock.json, plus the documentation described below.

---

🔧 Dependencies

Both are dev dependencies. The lockfile changes are limited to these two packages and the package's own version.

• @cldmv/fix-headers ^2.1.1 → ^2.2.0 (resolved 2.1.1 → 2.2.0; #39 moved it to 2.1.4 and #42 to 2.2.0). The 2.1.4 release no longer stamps a header into files that have no usable comment syntax (strict JSON such as package.json, and Markdown unless explicitly forced), never walks into node_modules or other dependency folders, and processes every repeated --input value instead of only the last. The 2.2.0 release changes what @Last modified by means: it now names whoever last edited a file's content, so a run that only rewrites a header (a date format conversion, a corrected @Project, new spacing) keeps the recorded editor instead of claiming the file for whoever ran the tool. The 2.1.2 and 2.1.3 releases in between were repository-maintenance releases with no change to the tool. It only runs through the fix:headers script; nothing that ships depends on it.
• @cldmv/configs ^1.2.0 → ^1.2.4 (#42). .configs/fix-headers.json extends @cldmv/configs/fix-headers.json, and from 1.2.4 that shared config sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false (both were true in 1.2.0). Together with fix-headers 2.2.0, a fix:headers run no longer overwrites @Author or @Last modified by on every file.

📚 Documentation

• NEW: docs/changelog/v0/v0.0.12.md: this changelog.
• Changelogs for earlier releases that shipped without one (v0.0.2 through v0.0.11) were added in the same pass (see the docs/changelog/ folder).
• README: a new What's New section with the Latest release and the four before it.

---

Upgrade notes

• No breaking changes, and no runtime code changed. It's a drop-in replacement for v0.0.11.
• For contributors: fix-headers 2.2.0 decides whether a file's content was edited by comparing the working tree with git HEAD, so run npm run fix:headers before committing, not after.

👥 Contributors

• @Shinrai

---

Metric	Coverage
Statements	100.0%
Branches	100.0%
Functions	100.0%
Lines	100.0%

Avg: 100.0% · f12f5a9 · Node lts/*

Co-authored-by: Shinrai Shinrai@users.noreply.github.com

[cldmv-bot]

🔒 Dependency Review

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses
• ✅ 0 denied package(s)
• ✅ 0 package(s) with OpenSSF Scorecard score < 3

Full job summary

[cldmv-bot]

📦 Bundle size unchanged

File	Raw	Δ Raw	Gzipped	Δ Gzipped
gitmulti.js	1.0 kB	—	622 B	—
Total	1.0 kB	±0 B	622 B	±0 B

_{📊 Generated by bundle-size. Brotli sizes also measured but omitted from the table for brevity.}