Skip to content

Releases: CLDMV/configs

v1.2.4

Choose a tag to compare

@cldmv-bot cldmv-bot released this 04 Oct 08:18
v1.2.4
a508c03

@cldmv/configs v1.2.4 Changelog

Release Date: October 2026
Release Type: Patch
Branch: release/1.2.4


Overview

The shared fix-headers.json stops forcing @Last modified by. Until now every fix-headers run in an extending repository stamped whoever ran it as the last modifier of every file it touched, even when the only change was a header rewrite such as a new date format. With forceLastModifiedAuthorUpdate set to false and fix-headers 2.2.0, @Last modified by now records the last person who actually edited a file's content, while @Last modified time still moves whenever fix-headers rewrites a header.

Together with forceAuthorUpdate: false, which shipped in v1.2.3, the shared config no longer rewrites anyone's authorship: @Author keeps the file's creator, and @Last modified by follows real edits. Extending repositories should upgrade to @cldmv/fix-headers 2.2.0 or later alongside this release.


🐛 Bug Fixes

@Last modified by follows real edits (#20)

forceLastModifiedAuthorUpdate was true, so every run rewrote @Last modified by to the identity running fix-headers (the name on their signing key, or git config user.name without one) on every file it changed. A contributor who ran npm run fix:headers therefore became the last modifier of every restamped file, even files they never opened (#15).

The option is now false. From fix-headers 2.2.0 (CLDMV/fix-headers#128) the field changes only when a file's content, everything outside the header, differs from the last commit, or when the file is new:

What changed in a file @Last modified time @Last modified by @Author
Nothing unchanged unchanged unchanged
Only the header (date format, epoch, @Date, spacing, filename, …) updated unchanged unchanged
Content edited, or a new file updated the person running fix-headers unchanged

On fix-headers releases before 2.2.0 the same setting keeps the existing @Last modified by on every run, real edits included, so the upgrade matters.

🔧 Dependencies

  • @cldmv/fix-headers ^2.1.4 → ^2.2.0 (#20), dev-only. The repository's own header pass ran under 2.2.0 and changed no files.
  • vitest and @vitest/coverage-v8 ^5.0.2 → ^5.0.3, and globals ^17.12.0 → ^17.13.0 (#21), dev-only. The coverage and globals bumps first merged as #18 and #19, two minutes after the v1.2.3 release, and were lost when next was reset after that release (CLDMV/.github#360). #21 re-applies them, together with the vitest bump from #17.

📚 Documentation

  • NEW: docs/changelog/v1/v1.2.4.md — this changelog.
  • README: the fix-headers.json table and notes explain both author settings, and the requirements now name fix-headers 2.2.0 as the version the author rules need.
  • v1.2.3 changelog corrected: that release also shipped forceAuthorUpdate: false, which its notes left out.

Upgrade notes

  • Upgrade @cldmv/fix-headers to 2.2.0 or later in every repository that extends this config. On older fix-headers, @Last modified by would no longer update even when a file is edited.
  • The first fix-headers run after upgrading leaves existing @Last modified by values alone and only changes them on files whose content was edited since the last commit. No repository-wide restamp of authors.

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · 117287f · Node lts/*

👥 Contributors

v1.2.3

Choose a tag to compare

@cldmv-bot cldmv-bot released this 04 Oct 06:37
v1.2.3
0106e9d

release: v1.2.3 - bump @cldmv/fix-headers to 2.1.4 and restamp file…

@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. Only header comments in repository-internal files changed (the ESLint and vitest configs, the pre-commit installer, Dependabot config, every workflow and the tests). This release also changed a published setting: fix-headers.json now sets forceAuthorUpdate to false (#16), so fix-headers keeps an existing @Author instead of rewriting it to whoever runs the tool.


🔧 CI & tooling

File headers restamped under fix-headers 2.1.4 (#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

🔧 Dependencies

  • @cldmv/fix-headers ^2.1.0 → ^2.1.4 (#12, dev-only).

Upgrade notes

  • fix-headers.json sets forceAuthorUpdate: false (#16): an existing @Author is kept. Otherwise drop-in for v1.2.2.

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · f3c80b1 · Node lts/*

👥 Contributors

v1.2.1

Choose a tag to compare

@cldmv-bot cldmv-bot released this 02 Oct 21:46
v1.2.1
840a007

release: v1.2.1 - stop the skipped PR-run mirror from satisfying… (#9)

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

No bug fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

  • #8
  • ci: stop the skipped PR-run mirror from satisfying Required PR Check
    (cfe1446)

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · dd34003 · Node lts/*


👥 Contributors

v1.1.1

Choose a tag to compare

@cldmv-bot cldmv-bot released this 29 Sep 06:13
v1.1.1
2dd2d7e

release: v1.1.1 - rewrite the README in the CLDMV package style

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

No bug fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

  • #3
    • docs: rewrite the README in the CLDMV package style (524e1d5)

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · 45f4a20 · Node lts/*

👥 Contributors

v1.1.0

Choose a tag to compare

@cldmv-bot cldmv-bot released this 29 Sep 05:54
v1.1.0
fdd4cc2

release: v1.1.0 - publish the shared fix-headers config (#2)

👥 Contributors