deps: bump @cldmv/fix-headers to 2.1.4 and restamp file headers - #12
Merged
Merged
Conversation
Bumps @cldmv/fix-headers to 2.1.4 and re-runs npm run fix:headers. 37 files' headers were restamped.
cldmv-bot
Bot
added
area: tests
Shinrai
approved these changes
Oct 4, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 4, 2026
# @cldmv/configs v1.2.3 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `release/1.2.3` --- ## Overview `@cldmv/fix-headers` moves to 2.1.4, and re-running the header pass with the repository's own `fix-headers.json` restamped the headers of 37 files — the first full pass under fix-headers 2.x since the repository moved to it in [v1.2.0](./v1.2.0.md). Only header comments in repository-internal files changed (the ESLint and vitest configs, the pre-commit installer, Dependabot config, every workflow and the tests). The published files — `fix-headers.json`, `README.md` and `LICENSE` — and every shipped setting are unchanged. --- ## 🔧 CI & tooling ### File headers restamped under fix-headers 2.1.4 ([#12](#12)) The 37 restamped headers changed in three ways: - **ISO 8601 dates.** Every `@Date` and `@Last modified time` is now written in git's `%aI` form (`2026-09-28T21:22:20-07:00`) instead of `2026-09-28 21:22:20 -07:00`, as the shared config's `normalizeDateFormat` asks. - **Corrected `@Date` epochs.** In 23 of the 37 headers — `.github/dependabot.yml` and 22 of the 28 workflow files, whose headers came from the `CLDMV/.github` templates — the Unix timestamp in parentheses did not match the date written beside it (for example `2026-05-20 00:00:00 -07:00 (1779606000)`, where 1779606000 is 24 May). fix-headers kept the written date and rewrote the timestamp to match it (`1779260400`). - **Header framing.** Each header gained an empty comment line just inside its opening and just before its closing (`/**` then ` *`, or a bare `#` in YAML), fix-headers' default `spacing` of one, while the single blank line after the header comes from the `margin: 1` that the repository's own `fix-headers.json` sets. `@Last modified time` was updated on every restamped file, as `forceLastModifiedAuthorUpdate` asks. ## 📚 Documentation - **NEW:** [docs/changelog/v1/v1.2.3.md](./v1.2.3.md) — this changelog, plus backfilled changelog files for [v1.1.0](./v1.1.0.md), [v1.1.1](./v1.1.1.md), [v1.2.0](./v1.2.0.md), [v1.2.1](./v1.2.1.md) and [v1.2.2](./v1.2.2.md). - README **✨ What's New** updated for v1.2.3, with **Recent Releases** linking the changelog files. ## 🔧 Dependencies - `@cldmv/fix-headers` `^2.1.0` → `^2.1.4` ([#12](#12), dev-only). --- ## Upgrade notes - No changes to `fix-headers.json` or any other published file — drop-in for v1.2.2. <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%** · `f3c80b1` · 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