release: v1.2.3 - bump @cldmv/fix-headers to 2.1.4 and restamp file… - #13
Merged
Merged
Conversation
Bumps @cldmv/fix-headers to 2.1.4 and re-runs npm run fix:headers. 37 files' headers were restamped.
Contributor
Author
🔒 Dependency Review
|
Contributor
Author
📦 Bundle size unchanged
📊 Generated by |
Drop forceAuthorUpdate from the shared config. With it on (together with useGpgSignerAuthor), anyone who ran fix-headers in an extending repository replaced every file's @author with their own name. @author records who created the file, so fix-headers' default of keeping it is the right house setting; a repository can still turn the option on for a one-off migration. Refs #15
Keep the option in the shared config as false instead of omitting it, so the decision is visible and overrides anything earlier in an extends chain.
Shinrai
approved these changes
Oct 4, 2026
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
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.
@cldmv/configs v1.2.3 Changelog
Release Date: October 2026
Release Type: Patch
Branch:
release/1.2.3Overview
@cldmv/fix-headersmoves to 2.1.4, and re-running the header pass with the repository's ownfix-headers.jsonrestamped 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). The published files —fix-headers.json,README.mdandLICENSE— and every shipped setting are unchanged.🔧 CI & tooling
File headers restamped under fix-headers 2.1.4 (#12)
The 37 restamped headers changed in three ways:
@Dateand@Last modified timeis now written in git's%aIform (2026-09-28T21:22:20-07:00) instead of2026-09-28 21:22:20 -07:00, as the shared config'snormalizeDateFormatasks.@Dateepochs. In 23 of the 37 headers —.github/dependabot.ymland 22 of the 28 workflow files, whose headers came from theCLDMV/.githubtemplates — the Unix timestamp in parentheses did not match the date written beside it (for example2026-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)./**then*, or a bare#in YAML), fix-headers' defaultspacingof one, while the single blank line after the header comes from themargin: 1that the repository's ownfix-headers.jsonsets.@Last modified timewas updated on every restamped file, asforceLastModifiedAuthorUpdateasks.📚 Documentation
🔧 Dependencies
@cldmv/fix-headers^2.1.0→^2.1.4(#12, dev-only).Upgrade notes
fix-headers.jsonor any other published file — drop-in for v1.2.2.👥 Contributors
Avg: 100.0% ·
f3c80b1· Node lts/*Co-authored-by: Shinrai Shinrai@users.noreply.github.com