Skip to content

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

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

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

Conversation

@cldmv-bot

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

Copy link
Copy Markdown
Contributor

Slothlet Vine v1.2.2 Changelog

Release Date: October 2026
Release Type: Patch
Branch: next → master


Overview

A dev-tooling dependency patch. The tools that maintain the comment headers at the top of the repository's source, test and config files move to their current releases: @cldmv/fix-headers from 2.1.1 to 2.2.0, and @cldmv/configs, the package that supplies the shared fix-headers configuration, from 1.2.0 to 1.2.4. No runtime source changed: the forwarding core, wire protocol, channel principal, around, event forwarding and every transport are exactly as in v1.2.1, and both peer ranges are unchanged (@cldmv/slothlet >=3.22.0, optional ws >=8.0.0).

The bumps were made with a header restamp in mind, but neither produced any header change in this repository: running npm run fix:headers against this release rewrites 0 files, so the only files touched are package.json and package-lock.json.


🔧 Dependencies

Both are dev dependencies. The lockfile changes are limited to these two packages and the package's own version.

  • @cldmv/fix-headers ^2.1.1 → ^2.2.0 (resolved 2.1.1 → 2.2.0; #72 moved it to 2.1.4 and #75 to 2.2.0). The 2.1.4 release no longer stamps a header into files that have no usable comment syntax (strict JSON such as package.json, and Markdown unless explicitly forced), never walks into node_modules or other dependency folders, and processes every repeated --input value instead of only the last. The 2.2.0 release changes what @Last modified by means: it now names whoever last edited a file's content, so a run that only rewrites a header (a date format conversion, a corrected @Project, new spacing) keeps the recorded editor instead of claiming the file for whoever ran the tool. The 2.1.2 and 2.1.3 releases in between were repository-maintenance releases with no change to the tool. It only runs through the fix:headers script; nothing in the published package depends on it.
  • @cldmv/configs ^1.2.0 → ^1.2.4 (#75). .configs/fix-headers.json extends @cldmv/configs/fix-headers.json, and from 1.2.4 that shared config sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false (both were true in 1.2.0). Together with fix-headers 2.2.0, a fix:headers run no longer overwrites @Author or @Last modified by on every file.

📚 Documentation

  • NEW: docs/changelog/v1/v1.2.2.md: this changelog.
  • README What's New: v1.2.2 is the new Latest, and v1.2.1 moves into Recent Releases.

Upgrade notes

  • No breaking changes, and no runtime code changed. It's a drop-in replacement for v1.2.1.
  • For contributors: fix-headers 2.2.0 decides whether a file's content was edited by comparing the working tree with git HEAD, so run npm run fix:headers before committing, not after.
👥 Contributors

coverage

Metric Coverage
Statements 98.2%
Branches 96.8%
Functions 98.6%
Lines 99.1%

Avg: 98.1% · e060195 · 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
schemas/frame.schema.json 1.5 kB — 512 B —
src/grow.mjs 22.5 kB — 8.4 kB —
src/index.mjs 1.7 kB — 924 B —
src/lib/errors.mjs 9.2 kB — 3.6 kB —
src/lib/events.mjs 16.5 kB — 5.7 kB —
src/lib/frame.mjs 14.6 kB — 5.1 kB —
src/lib/inbox.mjs 2.3 kB — 1.0 kB —
src/lib/link.mjs 7.5 kB — 2.9 kB —
src/lib/principal.mjs 11.8 kB — 4.3 kB —
src/serve.mjs 25.2 kB — 9.3 kB —
src/testing/conformance.mjs 10.6 kB — 3.3 kB —
src/transport/loopback.mjs 4.8 kB — 1.9 kB —
src/transport/post-message.mjs 11.8 kB — 4.4 kB —
src/transport/process.mjs 12.1 kB — 4.5 kB —
src/transport/websocket.mjs 11.8 kB — 4.4 kB —
src/transport/worker-threads.mjs 10.4 kB — 3.8 kB —
Total 174.3 kB ±0 B 64.0 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 18:53
Bumps @cldmv/fix-headers from 2.1.4 to 2.2.0. No file headers changed.
Range ^1.2.0 -> ^1.2.4.

The shared fix-headers.json in 1.2.4 sets forceAuthorUpdate and forceLastModifiedAuthorUpdate to false, so with @cldmv/fix-headers 2.2.0 @author is never rewritten and @last modified by changes only on real content edits.

Restamped 0 files; fix:headers made no changes.
@cldmv-bot
cldmv-bot Bot merged commit 8636ec6 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