docs: update the v0.0.12 release notes

README.md

@@ -5,7 +5,7 @@ Simple Node system to manage multiple Repositories into the same repo
 
 ### Latest: v0.0.12 (October 2026)
 
-- **Dev-tooling dependency bump ([#39](https://github.com/CLDMV/gitmulti/pull/39))** — `@cldmv/fix-headers` moves from 2.1.1 to 2.1.4, the tool that maintains the repository's file headers. It produced no header changes here, so only `package.json` and the lockfile changed. The CLI is unchanged; it's a drop-in replacement for the previous version.
+- **Dev-tooling dependency bump ([#39](https://github.com/CLDMV/gitmulti/pull/39), [#42](https://github.com/CLDMV/gitmulti/pull/42))** — `@cldmv/fix-headers` moves from 2.1.1 to 2.2.0, so `@Last modified by` now follows content edits only, and `@cldmv/configs` moves from 1.2.0 to 1.2.4, whose shared config no longer forces the author fields. Neither changed any file header here. The CLI is unchanged; it's a drop-in replacement for the previous version.
 - [View full v0.0.12 Changelog](https://github.com/CLDMV/gitmulti/blob/master/docs/changelog/v0/v0.0.12.md)
 
 ### Recent Releases

docs/changelog/v0/v0.0.12.md

@@ -8,23 +8,28 @@
 
 ## Overview
 
-A single dev-tooling dependency patch. `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test, config and workflow files, moves from 2.1.1 to 2.1.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.
+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 bump was made with a header restamp in mind, but fix-headers 2.1.4 produced no header changes in this repository, so the only files touched are `package.json` and `package-lock.json`.
+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
 
-- **`@cldmv/fix-headers` `2.1.1` → `2.1.4`** ([#39](https://github.com/CLDMV/gitmulti/pull/39)), dev dependency. The 2.1.x line 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. It only runs through the `fix:headers` script; nothing that ships depends on it.
+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](https://github.com/CLDMV/gitmulti/pull/39) moved it to 2.1.4 and [#42](https://github.com/CLDMV/gitmulti/pull/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](https://github.com/CLDMV/gitmulti/pull/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](./v0.0.12.md) — this changelog.
-- Changelogs for earlier releases that shipped without one were added in the same pass (see the [docs/changelog/](https://github.com/CLDMV/gitmulti/tree/master/docs/changelog/) folder).
+- **NEW:** [docs/changelog/v0/v0.0.12.md](./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/](https://github.com/CLDMV/gitmulti/tree/master/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.