deps: bump @cldmv/fix-headers to 2.1.4 and restamp file headers - #35
Merged
Merged
Conversation
Bumps @cldmv/fix-headers to 2.1.4 and re-runs npm run fix:headers. 0 files' headers were restamped.
cldmv-bot
Bot
added
! deps → next
Shinrai
approved these changes
Oct 4, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
# wol-proxy v1.0.10 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `next` → `master` --- ## Overview A dev-tooling dependency release. Three development dependencies move forward: `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test, config and workflow files (2.1.1 to 2.2.0), `@cldmv/configs`, the shared lint, format and header configuration (1.2.0 to 1.2.4), and `@cldmv/vitest-runner`, the test runner (1.2.0 to 1.5.3). No runtime code changed: `index.js`, `postinstall.js` and `wol-proxy.service` are exactly as in v1.0.9, and the runtime dependency ranges (`express` `^5.1.0`, `wake_on_lan` `^1.0.0`) and their lockfile entries are unchanged. The only other lockfile movement is `chalk` 5.6.2 to 6.0.1, a dev-only dependency of the test runner. No file headers were restamped by either fix-headers step, so the files touched are `package.json`, `package-lock.json` and the documentation. --- ## 🔧 Dependencies All dev-only; nothing that ships depends on them. - **`@cldmv/fix-headers` `^2.1.1` → `^2.2.0`** (locked 2.1.1 to 2.2.0), in two steps: 2.1.4 ([#35](#35)) and 2.2.0 ([#40](#40)). The 2.1.x line no longer stamps a header into files that have no usable comment syntax (strict JSON such as `package.json`, and Markdown unless explicitly forced), never walks into `node_modules` or other dependency folders, and processes every repeated `--input` value instead of only the last. From 2.2.0 the `@Last modified by` tag follows content edits only, so a header-only rewrite keeps the recorded editor. It only runs through the `fix:headers` script. Neither step changed any header in this repository. - **`@cldmv/configs` `^1.2.0` → `^1.2.4`** (locked 1.2.0 to 1.2.4) ([#40](#40)). Version 1.2.4 sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to `false`, so `@Author` is never rewritten and `@Last modified by` changes only on real content edits. Re-running `fix:headers` under the new config restamped no files. - **`@cldmv/vitest-runner` `^1.2.0` → `^1.5.3`** (locked 1.2.0 to 1.5.3) ([#38](#38)). This restores the bump from [#30](#30), which merged into `next` just after the previous release and was dropped by the post-release reset of `next` ([CLDMV/.github#360](CLDMV/.github#360)); it is reinstalled at the latest version instead of the original 1.5.1. The runner's own `chalk` dependency moves from `^5.4.1` to `^6.0.1` (locked 5.6.2 to 6.0.1), which requires Node 22 or newer; the CI matrix already starts at 22.12.0. ## 📚 Documentation - **NEW:** [docs/changelog/v1/v1.0.10.md](./v1.0.10.md) — this changelog. - Changelogs for earlier releases that shipped without one were added in the same pass (see the [docs/changelog/](https://github.com/CLDMV/wol-proxy/tree/master/docs/changelog/) folder). --- ## Upgrade notes - No breaking changes, and no runtime code changed. It's a drop-in replacement for v1.0.9. <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%** · `faa6d69` · 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