deps: bump @cldmv/vitest-runner from 1.2.0 to 1.5.1 in the minor group - #27
Merged
cldmv-bot[bot] merged 1 commit intoOct 2, 2026
Merged
Conversation
Bumps the minor group with 1 update: [@cldmv/vitest-runner](https://github.com/CLDMV/vitest-runner). Updates `@cldmv/vitest-runner` from 1.2.0 to 1.5.1 - [Release notes](https://github.com/CLDMV/vitest-runner/releases) - [Commits](CLDMV/vitest-runner@v1.2.0...v1.5.1) --- updated-dependencies: - dependency-name: "@cldmv/vitest-runner" dependency-version: 1.5.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
deleted the
dependabot/npm_and_yarn/next/minor-dca2327395
branch
October 2, 2026 19:16
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
# 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](#32) moved it to 2.1.4 and [#37](#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](#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](#35)), the test runner. This restores the bump from [#27](#27), which merged into `next` just after the previous release and was dropped by the post-release reset of `next` ([CLDMV/.github#360](CLDMV/.github#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. <details> <summary>👥 Contributors</summary> - @Shinrai </details> --- <!-- coverage-start -->  | Metric | Coverage | |--------|----------| | Statements | 100.0% | | Branches | 100.0% | | Functions | 100.0% | | Lines | 100.0% | *Avg: **100.0%** · `256f999` · Node lts/** <!-- coverage-end --> <!-- co-authors --> Co-authored-by: Shinrai <Shinrai@users.noreply.github.com>
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.
Bumps the minor group with 1 update: @cldmv/vitest-runner.
Updates
@cldmv/vitest-runnerfrom 1.2.0 to 1.5.1Release notes
Sourced from @cldmv/vitest-runner's releases.
... (truncated)
Commits
7aedb32release: v1.5.1 - backfill the missing v1.5.0 changelog9e0f31crelease: v1.5.0 - add an exclude option for test discovery1241f7frelease: v1.4.4 - drop the tsup-availability guard in prepack (#41)fade67frelease: v1.4.3 - enable minification for the tsup build0685350release: v1.4.2 - add missing repository/bugs/homepage fields to…ee919b6release: v1.4.1 - README npm badges reference the unscoped package name57542ferelease: v1.4.0 - bundle a real dist/ build with tsup, generate the CJS… (#22)cf7dcbdrelease: v1.3.3 - bump the npm_and_yarn group across 1 directory with 2… (#19)bf402bdbuild(deps-dev): bump the npm_and_yarn group across 1 directory with 2 update...c36611fMerge branch 'hotfixes' into hotfix-redirect/pr-8Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@cldmv/vitest-runnersince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions