deps: bump @cldmv/configs to 1.2.4 - #131
Merged
Merged
Conversation
cldmv-bot
Bot
added
! deps → next
Shinrai
approved these changes
Oct 5, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
# @cldmv/fix-headers v2.2.1 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `release/2.2.1` --- ## Overview Version 2.2.1 moves the repository's own development setup to `@cldmv/configs` 1.2.4. Nothing the package ships changed: `dist/`, `bin/`, the generated types and the runtime dependency `ignore` are exactly as in [v2.2.0](./v2.2.0.md). The published package differs only in the `version` field and in the `@cldmv/configs` range recorded in its `devDependencies`. The shared config is what the repository's own `npm run fix:headers` extends, so the bump changes how fix-headers stamps its own source files. Version 1.2.4 turns off `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate`, which were both on in 1.2.0. With v2.2.0 of the tool, that means `@Author` is never rewritten, and `@Last modified by` changes only when a file's content was edited. The run that accompanied the bump scanned 109 files and changed none. --- ## 🔧 Dependencies - **`@cldmv/configs` `^1.2.0` → `^1.2.4`** ([#131](#131)), dev dependency. The lockfile moves from 1.2.0 to 1.2.4, and that is the only dependency entry that changed. Between those versions the shared `fix-headers.json` switched `forceAuthorUpdate` (1.2.3) and `forceLastModifiedAuthorUpdate` (1.2.4) from `true` to `false`. It is used by `npm run fix:headers` and by nothing that ships. ## 📚 Documentation - **NEW:** [docs/changelog/v2/v2.2.1.md](./v2.2.1.md): this changelog. - README What's New promoted to v2.2.1. --- ## Upgrade notes - No breaking changes, and no behaviour change for consumers: drop-in for [v2.2.0](./v2.2.0.md). The runtime dependency list is unchanged. - Projects that extend `@cldmv/configs`' `fix-headers.json` should use `@cldmv/configs` 1.2.4 or later together with `@cldmv/fix-headers` 2.2.0 or later. On older versions of the tool, the forced author settings that 1.2.4 turns off behave differently. <details> <summary>👥 Contributors</summary> - @Shinrai </details> --- <!-- coverage-start -->  | Metric | Coverage | |--------|----------| | Statements | 100.0% | | Branches | 100.0% | | Functions | 100.0% | | Lines | 100.0% | *Avg: **100.0%** · `674426c` · 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
1 participant
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