docs: update the v1.1.4 release notes

README.md

@@ -17,6 +17,7 @@ On top of the literal syntax, jsonv adds **internal references** — file-scoped
 ### Latest: v1.1.4 (October 2026)
 
 - **`require()` returns the API synchronously** — `require("@cldmv/jsonv")` and `require("@cldmv/jsonv/<year>")` used to return a Promise of the ESM module; they now return the same exports as `import`, loaded through Node's `require(esm)`. Existing `await require(...)` code keeps working, but code that chained `.then()` on the `require()` result must use the result directly. CommonJS needs Node.js ^20.19.0 or >=22.12.0; older Node.js gets a clear `ERR_REQUIRE_ESM` pointing to `import()`. `@cldmv/jsonv/year-resolver` also gains the CommonJS wrapper it was missing (#80).
+- **Dev toolchain** — `@cldmv/fix-headers` 2.2.0 (`@Last modified by` now follows content edits only), `@cldmv/configs` 1.2.4, `@cldmv/vitest-runner` 1.5.1 and `typescript-eslint` 8.71.0, all dev-only; nothing was restamped (#77, #83, #85).
 - [View full v1.1.4 Changelog](https://github.com/CLDMV/jsonv/blob/master/docs/changelog/v1/v1.1.4.md)
 
 ### Recent Releases

docs/changelog/v1/v1.1.4.md

@@ -10,7 +10,7 @@
 
 Version 1.1.4 fixes the CommonJS entry points. Until now `require("@cldmv/jsonv")`, and every `require("@cldmv/jsonv/<year>")`, returned a Promise of the ESM module rather than the API, so CommonJS code had to `await` it. `require()` now returns the same exports as `import`, synchronously, loaded through Node's `require(esm)`.
 
-Existing `await require("@cldmv/jsonv")` code keeps working unchanged. Two cases do change and are covered in the upgrade notes below: code that chained `.then()` on the `require()` result, and CommonJS code on Node.js versions without `require(esm)`. The ESM API is untouched.
+Existing `await require("@cldmv/jsonv")` code keeps working unchanged. Two cases do change and are covered in the upgrade notes below: code that chained `.then()` on the `require()` result, and CommonJS code on Node.js versions without `require(esm)`. The ESM API is untouched. The dev toolchain is also refreshed (`@cldmv/fix-headers` 2.2.0, `@cldmv/configs` 1.2.4, `@cldmv/vitest-runner` 1.5.1, `typescript-eslint` 8.71.0); none of it ships in the package.
 
 ---
 
@@ -55,7 +55,9 @@ All development-only:
 
 - `@cldmv/vitest-runner` 1.4.3 → 1.5.1 ([#77](https://github.com/CLDMV/jsonv/pull/77))
 - `typescript-eslint` 8.70.1 → 8.71.0 ([#77](https://github.com/CLDMV/jsonv/pull/77))
-- `@cldmv/fix-headers` `^2.1.1` → `^2.1.4` ([#83](https://github.com/CLDMV/jsonv/pull/83)). Version 2.1.4 no longer writes a JavaScript comment into JSON or Markdown files, processes every repeated `--input`, and never walks dependency folders such as `node_modules`. Only `package.json` and the lockfile changed; no file headers were restamped.
+- `@cldmv/fix-headers` `^2.1.1` → `^2.2.0`, resolved to 2.2.0. The range was first raised to `^2.1.4` ([#83](https://github.com/CLDMV/jsonv/pull/83)) and then to `^2.2.0` ([#85](https://github.com/CLDMV/jsonv/pull/85)). Version 2.1.4 no longer writes a JavaScript comment into JSON or Markdown files, processes every repeated `--input`, and never walks dependency folders such as `node_modules`. Version 2.2.0 changes `@Last modified by` only when a file's content was edited, so header-only rewrites keep the recorded editor.
+- `@cldmv/configs` `^1.2.0` → `^1.2.4`, resolved to 1.2.4. The shared fix-headers config now sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to false ([#85](https://github.com/CLDMV/jsonv/pull/85)).
+- No file headers were restamped: each fix-headers bump changed only `package.json` and the lockfile.
 
 ---