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

README.md

@@ -3,6 +3,22 @@
 ## Description
 sizeofvar allows you to get a realistic memory size of any variable upon initialization or variable setting.  
 
+## ✨ What's New
+
+### Latest: v1.0.13 (October 2026)
+
+- **Dev-tooling dependency bumps ([#32](https://github.com/CLDMV/sizeofvar/pull/32), [#35](https://github.com/CLDMV/sizeofvar/pull/35), [#37](https://github.com/CLDMV/sizeofvar/pull/37))** — `@cldmv/fix-headers` moves from 2.1.1 to 2.2.0, so `@Last modified by` now follows content edits only, `@cldmv/configs` from 1.2.0 to 1.2.4, and the `@cldmv/vitest-runner` test runner from 1.2.0 to 1.5.3 (it now needs Node 22.12.0 or later, the floor CI already used). No file header changed. The `sizeofvar()` function is unchanged and the package still has no runtime dependencies; it's a drop-in replacement for the previous version.
+- [View full v1.0.13 Changelog](https://github.com/CLDMV/sizeofvar/blob/master/docs/changelog/v1/v1.0.13.md)
+
+### Recent Releases
+
+- **v1.0.12** (October 2026) — CI only: the in-repo PR mirror job now always runs and reports under a non-required name instead of being skipped ([Changelog](https://github.com/CLDMV/sizeofvar/blob/master/docs/changelog/v1/v1.0.12.md))
+- **v1.0.11** (October 2026) — CI only: a skipped PR-run mirror job no longer satisfies the `✅ Required PR Check` ruleset gate ([Changelog](https://github.com/CLDMV/sizeofvar/blob/master/docs/changelog/v1/v1.0.11.md))
+- **v1.0.10** (October 2026) — workflows synced to the CLDMV/.github v4.29.2 templates, bundle-size workflow, shared fix-headers config (comment-only header in `sizeofvar.js`); no runtime change ([Changelog](https://github.com/CLDMV/sizeofvar/blob/master/docs/changelog/v1/v1.0.10.md))
+- **v1.0.9** (September 2026) — vitest 5 test toolchain, a CI Node matrix of 22.12.0–26, and signed hotfix-redirector cherry-picks; no runtime change ([Changelog](https://github.com/CLDMV/sizeofvar/blob/master/docs/changelog/v1/v1.0.9.md))
+
+📚 **For complete version history and detailed release notes, see the [docs/changelog/](https://github.com/CLDMV/sizeofvar/tree/master/docs/changelog/) folder.**
+
 ## Install
 ```bash
 npm i @cldmv/sizeofvar --save

docs/changelog/v1/v1.0.1.md

@@ -0,0 +1,30 @@
+# sizeofvar v1.0.1 Changelog
+
+**Release Date**: March 2018
+**Release Type**: Patch
+
+---
+
+## Overview
+
+First release of sizeofvar, published to npm as `@cldmv/sizeofvar` (an unscoped `sizeofvar` package was published and withdrawn the same day). It bundles everything from the initial import on 2018-03-01 through the scoping of the package to CLDMV.
+
+---
+
+## ✨ Features
+
+- **`sizeofvar(value)`** estimates the V8 memory footprint of a value at initialization or assignment time. `sizeofvar.js` exports a single function that works out the type of the value (boolean, number, string, object, array) and returns a byte count using per-type base sizes.
+- **Recursion** — objects and arrays are walked recursively; nested members are costed with their own per-type adjustments, and objects with several keys add a per-key-group overhead. Top-level values and nested values use different base sizes.
+- **Numbers above 2^31** add an extra allocation, and numbers stored in arrays carry a small additional cost.
+- **Memory test harness** — `test/test-mem.js` plus per-type scripts under `test/sizeofvar/` (array, bool, number, object, object-complex, object-key-length, object-string, string) compare the returned number against what Node reports. It is run with `node --expose-gc test/test-mem.js <command> [-v]`, where `-v` enables verbose output. The harness uses `yargs` (a dev dependency) for argument parsing.
+- **Package** — scoped as `@cldmv/sizeofvar`, GPL-3.0, entry point `sizeofvar.js`, with a README covering install, usage and the test commands.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.1.md](./v1.0.1.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- First release; there is nothing to upgrade from. Install with `npm i @cldmv/sizeofvar --save`.

docs/changelog/v1/v1.0.10.md

@@ -0,0 +1,41 @@
+# sizeofvar v1.0.10 Changelog
+
+**Release Date**: October 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+A large CI and tooling sync. The only change to `sizeofvar.js` is an added comment header, so runtime behaviour is unchanged.
+
+---
+
+## 🔧 CI & tooling
+
+### Sync with CLDMV/.github v4.29.2 templates ([#21](https://github.com/CLDMV/sizeofvar/pull/21))
+
+Refreshes all workflow callers and adds `member-auto-merge.yml` (enables auto-merge on org members' PRs into `next`/`hotfixes`; does not approve), `pr-notify.yml`, `provenance.yml` (SLSA provenance on release) and `release-merge.yml`. `ci.yml`'s `max_node_major` now defaults to blank, inheriting the reusable workflow's default.
+
+### Bundle-size workflow ([#22](https://github.com/CLDMV/sizeofvar/pull/22))
+
+Adds `bundle-size.yml` (diffs `*.js` after `npm run build:ci` on PRs to `master`) and restores the full workflow list in the release-merge workflow.
+
+### Shared fix-headers config and uniform headers ([#24](https://github.com/CLDMV/sizeofvar/pull/24))
+
+Adds a `fix:headers` script and `.configs/fix-headers.json` extending `@cldmv/configs/fix-headers.json`, and stamps a uniform comment header onto `sizeofvar.js`, the tests and the workflow files. Comment headers only; no code changed in `sizeofvar.js`.
+
+## 🔧 Dependencies
+
+- New dev dependencies `@cldmv/configs` (`^1.2.0`) and `@cldmv/fix-headers` (`^2.1.1`).
+- vitest group and patch bumps ([#18](https://github.com/CLDMV/sizeofvar/pull/18), [#19](https://github.com/CLDMV/sizeofvar/pull/19), [#25](https://github.com/CLDMV/sizeofvar/pull/25), [#26](https://github.com/CLDMV/sizeofvar/pull/26)): `vitest` and `@vitest/coverage-v8` 5.0.0 → 5.0.2 in the lockfile only; `package.json` ranges stay `^5.0.0`. Dev dependencies, test/CI toolchain only.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.10.md](./v1.0.10.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.9. No runtime code changed.

docs/changelog/v1/v1.0.11.md

@@ -0,0 +1,28 @@
+# sizeofvar v1.0.11 Changelog
+
+**Release Date**: October 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+CI-only fix to the required-check job. No runtime code changed.
+
+---
+
+## 🔧 CI & tooling
+
+### Stop the skipped PR-run mirror from satisfying Required PR Check ([#28](https://github.com/CLDMV/sizeofvar/pull/28))
+
+On an in-repo feature PR the `pull_request` run skipped the `✅ Required PR Check` mirror job, and GitHub treats a skipped required check as passing, so a PR could become mergeable before the push run's tests finished. The job name became an expression so the skipped job no longer posts under the required name.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.11.md](./v1.0.11.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.10. No runtime code changed.

docs/changelog/v1/v1.0.12.md

@@ -0,0 +1,28 @@
+# sizeofvar v1.0.12 Changelog
+
+**Release Date**: October 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+CI-only follow-up to v1.0.11. No runtime code changed.
+
+---
+
+## 🔧 CI & tooling
+
+### Run the in-repo PR mirror job instead of skipping it ([#30](https://github.com/CLDMV/sizeofvar/pull/30))
+
+GitHub does not evaluate the `name:` of a skipped job, so v1.0.11's skipped job showed raw expression text. The mirror job now always runs; on the in-repo PR path it reports as `⏭️ Required PR Check (reported by the push run)` and exits as a no-op, while every status-owning path reports `✅ Required PR Check`.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.12.md](./v1.0.12.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.11. No runtime code changed.

docs/changelog/v1/v1.0.13.md

@@ -0,0 +1,37 @@
+# sizeofvar v1.0.13 Changelog
+
+**Release Date**: October 2026
+**Release Type**: Patch
+**Branch**: `next` → `master`
+
+---
+
+## Overview
+
+A dev-tooling dependency patch. Three development dependencies move to their current releases: `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test, config and workflow files, from 2.1.1 to 2.2.0; `@cldmv/configs`, the package that supplies the shared fix-headers configuration, from 1.2.0 to 1.2.4; and the `@cldmv/vitest-runner` test runner from 1.2.0 to 1.5.3. No runtime code changed: `sizeofvar.js` is exactly as in v1.0.12, and the package still has no runtime dependencies.
+
+The fix-headers 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`, plus the documentation described below.
+
+---
+
+## 🔧 Dependencies
+
+All of these are dev dependencies. The lockfile changes are limited to the packages below, the package's own version, and the one transitive package the test runner pulls in (`chalk`).
+
+- **`@cldmv/fix-headers` `^2.1.1` → `^2.2.0`** (resolved 2.1.1 → 2.2.0; [#32](https://github.com/CLDMV/sizeofvar/pull/32) moved it to 2.1.4 and [#37](https://github.com/CLDMV/sizeofvar/pull/37) 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 that ships depends on it.
+- **`@cldmv/configs` `^1.2.0` → `^1.2.4`** ([#37](https://github.com/CLDMV/sizeofvar/pull/37)). `.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.
+- **`@cldmv/vitest-runner` `^1.2.0` → `^1.5.3`** ([#35](https://github.com/CLDMV/sizeofvar/pull/35)), the test runner. This restores the bump from [#27](https://github.com/CLDMV/sizeofvar/pull/27), which merged into `next` just after the previous release and was dropped by the post-release reset of `next` ([CLDMV/.github#360](https://github.com/CLDMV/.github/issues/360)); it is reinstalled at the latest version instead of the original 1.5.1. The runner's own Node requirement rises from `>=20.19.0` to `>=22.12.0`, and its `chalk` dependency moves from 5.6.2 to 6.0.1 (Node 22 or later); the runner's package metadata also now declares Apache-2.0 instead of MIT. Test tooling only; nothing that ships depends on it.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.13.md](./v1.0.13.md): this changelog.
+- Changelogs for earlier releases that shipped without one (v1.0.1 through v1.0.12) were added in the same pass (see the [docs/changelog/](https://github.com/CLDMV/sizeofvar/tree/master/docs/changelog/) folder).
+- README: a new **What's New** section with the Latest release and the four before it.
+
+---
+
+## Upgrade notes
+
+- No breaking changes, and no runtime code changed. It's a drop-in replacement for v1.0.12.
+- For contributors: running the test suite now needs Node.js 22.12.0 or later, which is the floor the CI matrix has used since v1.0.9. The package itself declares no `engines`, and consumers are unaffected.
+- 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.

docs/changelog/v1/v1.0.2.md

@@ -0,0 +1,22 @@
+# sizeofvar v1.0.2 Changelog
+
+**Release Date**: March 2018
+**Release Type**: Patch
+
+---
+
+## Overview
+
+Version-only bump. `package.json` moved from 1.0.1 to 1.0.2 and nothing else changed. There are no code changes in this release and it was not published to npm.
+
+---
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.2.md](./v1.0.2.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes. No code changes; this version was tagged but not published to npm, so v1.0.1 → v1.0.3 is the effective upgrade path.

docs/changelog/v1/v1.0.3.md

@@ -0,0 +1,23 @@
+# sizeofvar v1.0.3 Changelog
+
+**Release Date**: March 2018
+**Release Type**: Patch
+
+---
+
+## Overview
+
+Documentation fix: the README install command now uses the scoped package name. No runtime code changed.
+
+---
+
+## 📚 Documentation
+
+- README install command changed from `npm i sizeofvar --save` to `npm i @cldmv/sizeofvar --save`.
+- **NEW:** [docs/changelog/v1/v1.0.3.md](./v1.0.3.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.2. Only the README and version changed; `sizeofvar.js` is untouched.

docs/changelog/v1/v1.0.4.md

@@ -0,0 +1,23 @@
+# sizeofvar v1.0.4 Changelog
+
+**Release Date**: March 2018
+**Release Type**: Patch
+
+---
+
+## Overview
+
+Documentation fix: the README usage example now requires the scoped package name. No runtime code changed.
+
+---
+
+## 📚 Documentation
+
+- README usage example changed from `require('sizeofvar')` to `require('@cldmv/sizeofvar')`.
+- **NEW:** [docs/changelog/v1/v1.0.4.md](./v1.0.4.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.3. Only the README and version changed; `sizeofvar.js` is untouched.

docs/changelog/v1/v1.0.5.md

@@ -0,0 +1,47 @@
+# sizeofvar v1.0.5 Changelog
+
+**Release Date**: August 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+First release through the CLDMV v4 `next` → `master` release flow, and the first after a long gap: the previous release was v1.0.4 in 2018. It adds the CI/release workflows and replaces the old memory-harness scripts with a vitest suite. `sizeofvar.js` is unchanged, so runtime behaviour is identical to v1.0.4.
+
+It also carries a 2019 README addition (a contributors section) that had never been released.
+
+---
+
+## 🔧 CI & tooling
+
+### Adopt CLDMV @v4 workflows + vitest-runner tests ([#2](https://github.com/CLDMV/sizeofvar/pull/2))
+
+Adds the v4 staging-branch workflow set under `.github/workflows/` (CI, publish, feature-pr, next-release, hotfixes-release, next-reset, hotfix-redirector, labeler, pr-title-normalizer, master-commit-audit, release-notify, tag-health, update-major-version-tags, v4-bootstrap, cla, codeql, scorecard, dependency-review, dependabot-auto-merge, stale, welcome, branch-retention), all thin callers of `CLDMV/.github` reusables pinned `@v4`, plus `.github/dependabot.yml`. Releases now go through the `next` → `master` release PR.
+
+### Build script stub for the coverage job ([#4](https://github.com/CLDMV/sizeofvar/pull/4))
+
+Adds `build` and `build:ci` scripts that only echo, because the coverage-badge job runs `npm run build`. The package has no build step.
+
+### Vitest suite replaces the memory harness ([#2](https://github.com/CLDMV/sizeofvar/pull/2))
+
+- The old `test/test-mem.js` harness and the `test/sizeofvar/*.js` scripts are removed, replaced by vitest tests in `tests/` (arrays, booleans, edge types, numbers, objects, random properties, strings) with `.configs/vitest.config.mjs` and a `tests/run-vitest.mjs` runner.
+- New scripts: `test`, `test:watch`, `coverage`, `ci:coverage`. The previous `test` script was an `echo` stub.
+- The `node --expose-gc test/test-mem.js` instructions are no longer applicable.
+
+## 🔧 Dependencies
+
+- Removed the `yargs` devDependency. Its only use at the previous release (`git grep`) was argument parsing in the deleted `test/test-mem.js` harness, so nothing remained that used it.
+- Added dev dependencies `@cldmv/vitest-runner`, `vitest` and `@vitest/coverage-v8` (`^4.1.10`). These affect only the test/CI toolchain, not consumers.
+- Added `publishConfig.access: public`.
+
+## 📚 Documentation
+
+- README gains a Contributors section (committed in 2019, first released here).
+- **NEW:** [docs/changelog/v1/v1.0.5.md](./v1.0.5.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.4. The exported function is unchanged; only repository tooling, tests and dev dependencies changed.

docs/changelog/v1/v1.0.6.md

@@ -0,0 +1,29 @@
+# sizeofvar v1.0.6 Changelog
+
+**Release Date**: August 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+Test-file rename. Test files move to the fleet-wide `*.test.vitest.mjs` naming convention and the vitest config and runner are updated to match. No runtime code changed.
+
+---
+
+## 🔧 CI & tooling
+
+### Wire vitest config + runner to the new test-file suffix ([#6](https://github.com/CLDMV/sizeofvar/pull/6))
+
+- `tests/*.test.mjs` renamed to `tests/*.test.vitest.mjs` (pure renames, contents unchanged).
+- `.configs/vitest.config.mjs`, `tests/run-vitest.mjs` and the `package.json` scripts updated to the new pattern.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.6.md](./v1.0.6.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.5. No runtime code changed.

docs/changelog/v1/v1.0.7.md

@@ -0,0 +1,28 @@
+# sizeofvar v1.0.7 Changelog
+
+**Release Date**: August 2026
+**Release Type**: Patch
+
+---
+
+## Overview
+
+CI-only release. The CI concurrency rules are changed so release-relevant runs are never cancelled. No runtime code changed.
+
+---
+
+## 🔧 CI & tooling
+
+### Never supersede release-relevant CI runs ([#8](https://github.com/CLDMV/sizeofvar/pull/8))
+
+`ci.yml` concurrency now gives pushes to the release base branch, to `next`/`hotfixes`, and the `next`/`hotfixes` release PRs a unique concurrency group per run; feature branches still cancel superseded runs. Previously a burst of pushes during a release could cancel a pending run and leave a red cancelled check on the release PR.
+
+## 📚 Documentation
+
+- **NEW:** [docs/changelog/v1/v1.0.7.md](./v1.0.7.md) — this changelog (added retroactively).
+
+---
+
+## Upgrade notes
+
+- No breaking changes — drop-in for v1.0.6. No runtime code changed.