deps: bump @cldmv/fix-headers to 2.2.0 - #40
Merged
Merged
Conversation
Bumps @cldmv/fix-headers from 2.1.4 to 2.2.0. No file headers changed.
Raises the range from ^1.2.0 (locked 1.2.0) to ^1.2.4. Configs 1.2.4 sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false, so with fix-headers 2.2.0 @author is never rewritten and @last modified by changes only on real content edits. Ran fix:headers under the new config: 0 files restamped.
Shinrai
approved these changes
Oct 5, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
# @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](./v1.0.11.md) — this changelog, plus backfilled changelog files for every earlier release, [v1.0.2](./v1.0.2.md) through [v1.0.10](./v1.0.10.md). - **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](#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](#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](#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. --- ## Upgrade notes - No runtime changes — drop-in for v1.0.10. <details> <summary>👥 Contributors</summary> - @Shinrai </details> --- <!-- coverage-start -->  | Metric | Coverage | |--------|----------| | Statements | 32.8% | | Branches | 25.3% | | Functions | 50.7% | | Lines | 32.9% | *Avg: **35.4%** · `c7f8069` · Node lts/** <!-- coverage-end --> <!-- co-authors --> Co-authored-by: Shinrai <Shinrai@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
No new features
🐛 Bug Fixes
No bug fixes
📦 Dependencies
🔧 Other Changes
No other changes
👥 Contributors