Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

### Latest: v1.0.11 (October 2026)

- **Header tooling on fix-headers 2.1.4** β€” the `@cldmv/fix-headers` dev dependency moves to 2.1.4 and the header pass was re-run; every file already matched, so nothing was restamped. No library or CLI code changed (#34).
- **Header tooling on fix-headers 2.2.0** β€” the `@cldmv/fix-headers` dev dependency moves to 2.2.0 and `@cldmv/configs` to 1.2.4, so `@Last modified by` now follows content edits only. Every file already matched, so nothing was restamped, and no library or CLI code changed (#34, #40).
- **Complete version history** β€” every release from v1.0.2 onward now has a changelog under [docs/changelog/](https://github.com/CLDMV/envm/tree/master/docs/changelog/). v1.0.2 is the only version published to npm so far; v1.0.3 through v1.0.10 changed tooling, CI and documentation only, with no change to the library or CLI.
- [View full v1.0.11 Changelog](https://github.com/CLDMV/envm/blob/master/docs/changelog/v1/v1.0.11.md)

Expand Down
7 changes: 5 additions & 2 deletions docs/changelog/v1/v1.0.11.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

## Overview

A dev-dependency release: `@cldmv/fix-headers` moves to 2.1.4 and the header pass was re-run. Every header already matched what 2.1.4 writes, so no file was restamped. No library or CLI code, published file or dependency used at runtime changed.
A dev-dependency release. `@cldmv/fix-headers` moves from 2.1.1 to 2.2.0, passing through 2.1.4, and the shared `@cldmv/configs` config moves from 1.2.0 to 1.2.4. Both header passes were re-run and every header already matched what the new versions write, so no file was restamped: the net change to the repository outside documentation is the two version ranges in `package.json` and the lockfile. No library or CLI code, published file or dependency used at runtime changed.

---

Expand All @@ -19,7 +19,10 @@ A dev-dependency release: `@cldmv/fix-headers` moves to 2.1.4 and the header pas

## πŸ”§ Dependencies

- `@cldmv/fix-headers` 2.1.1 β†’ 2.1.4 ([#34](https://github.com/CLDMV/envm/pull/34), dev-only).
Both are dev-only and affect only the `npm run fix:headers` script, which extends `@cldmv/configs/fix-headers.json`.

- `@cldmv/fix-headers` `^2.1.1` β†’ `^2.2.0`, in two steps. 2.1.4 ([#34](https://github.com/CLDMV/envm/pull/34)) stops the tool from writing comment headers into files that cannot carry one, such as strict JSON, and from walking `node_modules`. 2.2.0 ([#40](https://github.com/CLDMV/envm/pull/40)) makes `@Last modified by` follow edits to a file's content only, so a run that merely rewrites a header keeps the recorded editor.
- `@cldmv/configs` `^1.2.0` β†’ `^1.2.4` ([#40](https://github.com/CLDMV/envm/pull/40)). The shared fix-headers config now sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to `false`, so `@Author` keeps the file's creator and `@Last modified by` changes only with real content edits. The 1.2.1 and 1.2.2 releases of that package only changed its own CI.

---

Expand Down
Loading