Skip to content

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

Merged
cldmv-bot[bot] merged 9 commits into
masterfrom
next
Oct 4, 2026
Merged

cldmv-bot[bot] merged 9 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

@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). 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)

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

  • No changes to fix-headers.json or any other published file — drop-in for v1.2.2.
👥 Contributors

coverage

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

Avg: 100.0% · f3c80b1 · Node lts/*

Co-authored-by: Shinrai Shinrai@users.noreply.github.com

@cldmv-bot cldmv-bot Bot added ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes area: tests Touches test files, fixtures, or test infrastructure type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: dependencies Relates to dependency updates, version bumps, or package management labels Oct 4, 2026
@cldmv-bot

cldmv-bot Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author

🔒 Dependency Review

  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ✅ 0 package(s) with unknown licenses
  • ✅ 0 denied package(s)
  • ✅ 0 package(s) with OpenSSF Scorecard score < 3

Full job summary

@cldmv-bot

cldmv-bot Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author

📦 Bundle size unchanged

File Raw Δ Raw Gzipped Δ Gzipped
fix-headers.json 319 B +1 B (+0.3%) 217 B +5 B
Total 319 B +1 B 217 B +5 B

📊 Generated by bundle-size. Brotli sizes also measured but omitted from the table for brevity.

@cldmv-bot cldmv-bot Bot added the type: documentation Relates to docs, README updates, guides, or inline code comments label Oct 4, 2026
Shinrai and others added 3 commits October 3, 2026 22:44
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.
@cldmv-bot cldmv-bot Bot added the type: bug Something is broken or not behaving as expected label Oct 4, 2026
@cldmv-bot
cldmv-bot Bot merged commit 0106e9d into master Oct 4, 2026
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: tests Touches test files, fixtures, or test infrastructure ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: dependencies Relates to dependency updates, version bumps, or package management type: documentation Relates to docs, README updates, guides, or inline code comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant