Repository navigation
@cldmv/envm v1.0.11 Changelog
Release Date: October 2026
Release Type: Patch
Branch: release/1.0.11
Overview
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.
📚 Documentation
- NEW: docs/changelog/v1/v1.0.11.md — this changelog, plus backfilled changelog files for every earlier release, v1.0.2 through v1.0.10.
- NEW: README ✨ What's New section.
🔧 Dependencies
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) stops the tool from writing comment headers into files that cannot carry one, such as strict JSON, and from walkingnode_modules. 2.2.0 (#40) makes@Last modified byfollow 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). The shared fix-headers config now setsforceAuthorUpdateandforceLastModifiedAuthorUpdatetofalse, so@Authorkeeps the file's creator and@Last modified bychanges only with real content edits. The 1.2.1 and 1.2.2 releases of that package only changed its own CI.
Upgrade notes
- No runtime changes — drop-in for v1.0.10.
| Metric | Coverage |
|---|---|
| Statements | 32.8% |
| Branches | 25.3% |
| Functions | 50.7% |
| Lines | 32.9% |
Avg: 35.4% · c7f8069 · Node lts/*