deps: bump @cldmv/fix-headers to 2.2.0 - #78
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
Bump @cldmv/configs ^1.2.1 (locked 1.2.1) to ^1.2.4 (1.2.4). The older shared fix-headers.json forced forceAuthorUpdate and forceLastModifiedAuthorUpdate on; 1.2.4 sets both false, so with fix-headers 2.2.0 @author is never rewritten and @last modified by changes only on real content edits. Restamped files: 0.
Shinrai
approved these changes
Oct 5, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
# vitest-runner v1.5.4 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `next` → `master` --- ## Overview A dev-tooling dependency release with no change to the published package. Two development dependencies move forward, `@cldmv/fix-headers` (the tool that maintains the comment headers at the top of source, test, config and workflow files) and `@cldmv/configs` (the shared lint, format and header configuration), and the dev-only transitive `brace-expansion` is patched to 5.0.12. Nothing under `src/`, `tests/`, `bin/` or the build configuration changed, so `dist/` and the CLI, the `run()` API and the CommonJS entry are identical to [v1.5.3](./v1.5.3.md). The runtime dependency and peer ranges are untouched, and the only lockfile entries that moved are the three below. No file headers were restamped: both fix-headers steps and the configs bump re-ran `fix:headers` and changed no file. --- ## 🔧 Dependencies All dev-only; none of them is installed by consumers of the package. - **`@cldmv/fix-headers` `^2.1.2` → `^2.2.0`** (locked 2.1.2 to 2.2.0), in two steps: 2.1.4 ([#74](#74)) and 2.2.0 ([#78](#78)). Version 2.1.4 never adds a JS comment header to JSON, Markdown or extension-less files and never walks into dependency folders. From 2.2.0 the `@Last modified by` tag follows content edits only, so a header-only rewrite keeps the recorded editor. - **`@cldmv/configs` `^1.2.1` → `^1.2.4`** (locked 1.2.1 to 1.2.4) ([#78](#78)). The older shared `fix-headers.json` forced `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` on; version 1.2.4 sets both to `false`, so `@Author` is never rewritten and `@Last modified by` changes only on real content edits. - **`brace-expansion` 5.0.9 → 5.0.12**, an indirect dev dependency (pulled in through `minimatch`), updated by Dependabot's `npm_and_yarn` group ([#76](#76)). Lockfile only; `package.json` does not list it. ## 📚 Documentation - **NEW:** [docs/changelog/v1/v1.5.4.md](./v1.5.4.md): this changelog. - README What's New promoted to v1.5.4. --- ## Upgrade notes - No breaking changes and no change to what the package ships: a drop-in replacement for [v1.5.3](./v1.5.3.md). The Node.js 22.12 floor introduced in v1.5.3 is unchanged. <details> <summary>👥 Contributors</summary> - @Shinrai </details> --- <!-- coverage-start -->  | Metric | Coverage | |--------|----------| | Statements | 99.4% | | Branches | 99.6% | | Functions | 100.0% | | Lines | 99.3% | *Avg: **99.5%** · `37726c2` · 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