deps: bump @cldmv/fix-headers to 2.2.0 - #54
Merged
Merged
Conversation
Bumps @cldmv/fix-headers from 2.1.4 to 2.2.0. No file headers changed.
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/prettier-plugin-jsonv v1.1.4 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `release/1.1.4` --- ## Overview A dev-dependency release: `@cldmv/fix-headers` moves to 2.2.0 and `@cldmv/configs` to 1.2.4. The header pass was re-run for 2.1.4, and every header already matched what that version writes, so no file was restamped; the 2.2.0 and 1.2.4 bumps changed only `package.json` and the lockfile. No plugin code, published file or runtime dependency changed. --- ## 📚 Documentation - **NEW:** [docs/changelog/v1/v1.1.4.md](./v1.1.4.md) — this changelog, plus backfilled changelog files for [v1.1.1](./v1.1.1.md), [v1.1.2](./v1.1.2.md) and [v1.1.3](./v1.1.3.md). - README **✨ What's New** updated for v1.1.4. ## 🔧 Dependencies Both changes are to development dependencies. The runtime `peerDependencies` and the published package are unchanged. - `@cldmv/fix-headers` `^2.1.1` → `^2.2.0` ([#51](#51) took it to `^2.1.4`, [#54](#54) to `^2.2.0`). 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 makes the `@Last modified by` header tag follow content edits only, so a header-only rewrite keeps the recorded editor instead of replacing it. It requires Node.js `>=22.12.0`, the same floor as the rest of the development toolchain. - `@cldmv/configs` `^1.2.0` → `^1.2.4` ([#54](#54)). It provides the shared `fix-headers` configuration that `.configs/fix-headers.json` extends. Version 1.2.4 turns off `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` (both were on in 1.2.0), so the shared configuration no longer overwrites the recorded author or last editor. - Despite its title, [#51](#51) (`restamp file headers`) changed only `package.json` and the lockfile. Neither it nor [#54](#54) restamped any header. --- ## Upgrade notes - No runtime changes — drop-in for v1.1.3. <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%** · `5893750` · 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