Skip to content

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

Merged
cldmv-bot[bot] merged 11 commits into
masterfrom
next
Oct 5, 2026
Merged

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

Conversation

@cldmv-bot

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

Copy link
Copy Markdown
Contributor

@cldmv/envm v1.0.11 Changelog

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


Overview

A dev-dependency release. @cldmv/fix-headers moves from 2.1.1 to 2.2.0, passing through 2.1.4, and the shared @cldmv/configs config moves from 1.2.0 to 1.2.4. Both header passes were re-run and every header already matched what the new versions write, so no file was restamped: the net change to the repository outside documentation is the two version ranges in package.json and the lockfile. No library or CLI code, published file or dependency used at runtime changed.


📚 Documentation

🔧 Dependencies

Both are dev-only and affect only the npm run fix:headers script, which extends @cldmv/configs/fix-headers.json.

  • @cldmv/fix-headers ^2.1.1 → ^2.2.0, in two steps. 2.1.4 (#34) stops the tool from writing comment headers into files that cannot carry one, such as strict JSON, and from walking node_modules. 2.2.0 (#40) makes @Last modified by follow edits to a file's content only, so a run that merely rewrites a header keeps the recorded editor.
  • @cldmv/configs ^1.2.0 → ^1.2.4 (#40). The shared fix-headers config now sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false, so @Author keeps the file's creator and @Last modified by changes only with real content edits. The 1.2.1 and 1.2.2 releases of that package only changed its own CI.

Upgrade notes

  • No runtime changes — drop-in for v1.0.10.
👥 Contributors

coverage

Metric Coverage
Statements 32.8%
Branches 25.3%
Functions 50.7%
Lines 32.9%

Avg: 35.4% · c7f8069 · 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 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
dist/backup.mjs 1.8 kB — 988 B —
dist/cli.mjs 1.8 kB — 917 B —
dist/index.mjs 921 B — 359 B —
dist/path-utils.mjs 408 B — 262 B —
dist/platform/posix.mjs 4.6 kB — 1.5 kB —
dist/platform/win.mjs 4.2 kB — 1.4 kB —
Total 13.7 kB ±0 B 5.3 kB ±0 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 5 commits October 4, 2026 16:39
Bumps @cldmv/fix-headers from 2.1.4 to 2.2.0. No file headers changed.
Raises the range from ^1.2.0 (locked 1.2.0) to ^1.2.4. Configs 1.2.4 sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false, so with fix-headers 2.2.0 @author is never rewritten and @last modified by changes only on real content edits. Ran fix:headers under the new config: 0 files restamped.
@cldmv-bot
cldmv-bot Bot merged commit 4a4b576 into master Oct 5, 2026
42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! 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: 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