Skip to content

deps: bump the patch group across 1 directory with 11 updates - #114

Open
dependabot[bot] wants to merge 1 commit into
nextfrom
dependabot/npm_and_yarn/next/patch-9ce575c5e0
Open

dependabot[bot] wants to merge 1 commit into
nextfrom
dependabot/npm_and_yarn/next/patch-9ce575c5e0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 21, 2026 •

Copy link
Copy Markdown

Bumps the patch group with 11 updates in the / directory:

Package From To
@cldmv/slothlet 3.22.0 3.22.1
@cldmv/wisp 1.0.6 1.0.8
@cldmv/eslint-plugin-jsonv 1.0.15 1.0.17
@cldmv/fix-headers 2.2.0 2.2.2
@cldmv/jsonv 1.1.3 1.1.5
@cldmv/prettier-plugin-jsonv 1.1.3 1.1.4
@cldmv/vitest-runner 1.5.3 1.5.4
@eslint/css 2.0.0 2.0.1
@eslint/json 2.1.0 2.1.1
@vitest/coverage-v8 5.0.3 5.0.5
vitest 5.0.3 5.0.5

Updates @cldmv/slothlet from 3.22.0 to 3.22.1

Release notes

Sourced from @​cldmv/slothlet's releases.

@​cldmv/slothlet-types v3.22.1

Part of @cldmv/slothlet v3.22.1 — built from the same commit and published at the same version.

Commits
  • d135d07 release: v3.22.1 - bump @​cldmv/fix-headers from 1.3.12 to 2.1.0
  • See full diff in compare view

Updates @cldmv/wisp from 1.0.6 to 1.0.8

Release notes

Sourced from @​cldmv/wisp's releases.

v1.0.8

@cldmv/wisp v1.0.8 Changelog

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


Overview

A one-line development-dependency patch: @types/node 26.6.3 → 26.6.4 (#46). The only files that differ from v1.0.7 are package.json (the version number) and package-lock.json. The package.json range ^26.6.2 already allowed the new version, so the lockfile is the only place the bump is recorded.

@types/node is a development dependency used by the TypeScript type check (npm run types:check, part of npm run build:ci). It does not enter the published tarball, which still contains only dist/, types/, README.md and LICENSE, and the package still has no runtime dependencies. With the bump in place npm run build:ci (lint, format check, tsc, the build, the test suite and the type check) passes.


🔧 Dependencies

  • @types/node 26.6.3 → 26.6.4 (#46), a lockfile-only patch update within the existing ^26.6.2 range. It is the only entry in the lockfile that changed, and its declared dependencies are unchanged.

📚 Documentation


Upgrade notes

  • No breaking changes and no runtime change: drop-in for v1.0.7. engines.node (>=16.0.0) is unchanged, and the supported Node.js versions for import and require() are the same.

coverage

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

Avg: 100.0% · 3595850 · Node lts/*

... (truncated)

Commits
  • 2e0ad68 release: v1.0.8 - Bump @​types/node from 26.6.3 to 26.6.4 in the patch…
  • 4f7f995 release: v1.0.7 - require the ESM entry directly and fail clearly on…
  • See full diff in compare view
Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Updates @cldmv/eslint-plugin-jsonv from 1.0.15 to 1.0.17

Release notes

Sourced from @​cldmv/eslint-plugin-jsonv's releases.

v1.0.17

@cldmv/eslint-plugin-jsonv v1.0.17 Changelog

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


Overview

A dev-dependency release: eslint 10.12.0, globals 17.13.0, vitest 5.0.3, @cldmv/vitest-runner 1.5.3, the @cldmv/jsonv and @cldmv/prettier-plugin-jsonv 1.1.3 releases, and @types/node 26.6.4. One consequence worth knowing about: the test runner now declares Node.js 22.12 as its minimum, which is stricter than the ^20.19.0 entry in this package's own engines range, and it pulls in chalk 6.

No plugin code, published file or declared dependency range changed. The net diff against v1.0.16 is the lockfile and the version field of package.json; every range in package.json (including the eslint and @cldmv/jsonv peer ranges and the dev ranges) is untouched, so each update below is a lockfile-only move within an existing range. The package has no dependencies, only the two peers, and every package that moved is a development dependency or a transitive of one.


🔧 Dependencies

All updates are development-only, grouped by Dependabot into four pull requests (#59, #60, #62, #64).

  • eslint 10.11.0 → 10.12.0 (#60). This is the version the plugin's tests and lint run against. The published eslint peer range (^9.13.0 || ^10.0.0) is unchanged.
  • globals 17.12.0 → 17.13.0 (#62).
  • vitest 5.0.2 → 5.0.3 (#59), with @vitest/coverage-v8, @vitest/mocker and @vitest/spy following to 5.0.3. Transitive: vite 8.3.1 → 8.3.2, rolldown and its platform bindings 1.2.11 → 1.2.12, @oxc-project/types 0.151.0 → 0.152.0, and why-is-node-running 3.2.2 → 3.2.1 (pinned by vitest 5.0.3).
  • @cldmv/vitest-runner 1.5.1 → 1.5.3 (#64). The runner's 1.5.3 release makes its CommonJS entry fail with a clear error on a Node.js version without require(esm) and raises its engines.node from >=20.19.0 to >=22.12.0. The locked package's license field also changes from MIT to Apache-2.0. Its chalk dependency moves from 5.x to 6, so the locked chalk goes 5.6.2 → 6.0.1 with engines changing from ^12.17.0 || ^14.13 || >=16.0.0 to >=22. Both are reached only through the test runner.
  • @cldmv/jsonv 1.1.1 → 1.1.3 and @cldmv/prettier-plugin-jsonv 1.1.0 → 1.1.3 (#64). Their releases are CI-workflow changes in those repositories (the in-repo PR mirror job now runs instead of being skipped) plus a tooling bump in @cldmv/jsonv. Both still declare node >=18.0.0, and the prettier plugin's peer ranges are unchanged. @cldmv/jsonv is also a peer dependency of the published plugin (^1.1.0, unchanged); the move to 1.1.3 only changes which version the plugin's own tests run against, and 1.1.3 satisfies that range.
  • @types/node 26.6.3 → 26.6.4 (#64).

Node.js floors

This package's engines.node stays ^20.19.0 || ^22.13.0 || >=24, and that range describes who can install and run the plugin, which depends on none of the packages above. The development toolchain already required Node.js 22.12 (vitest 5, @cldmv/fix-headers), and @cldmv/vitest-runner now says so too. The CI matrix starts at 22.12.0, so CI is unaffected; a contributor on Node.js 20 cannot run the test suite, as before.


📚 Documentation


Upgrade notes

  • No runtime changes: drop-in for v1.0.16. The published files, the eslint peer range and the supported Node.js range for consumers are unchanged.

coverage

... (truncated)

Commits
  • d8d54ec release: v1.0.17 - bump the patch group across 1 directory with 4 updates
  • 4964450 release: v1.0.16 - bump @​cldmv/fix-headers to 2.1.4 and restamp file…
  • See full diff in compare view

Updates @cldmv/fix-headers from 2.2.0 to 2.2.2

Release notes

Sourced from @​cldmv/fix-headers's releases.

v2.2.2

@cldmv/fix-headers v2.2.2 Changelog

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


Overview

Version 2.2.2 is a dependency refresh. Everything that changed is in package-lock.json: the package.json ranges are untouched, and the only change to package.json is the version number. The source, dist/, bin/, the generated types and the declared dependency ranges are exactly as in v2.2.1.

One runtime dependency moved inside its existing range: ignore 7.0.10 → 7.0.12. It is the only dependency fix-headers declares (^7.0.5), and it is kept external by the build, so it is not bundled into dist/. A consumer's install already resolves ignore from that range, so a published 2.2.2 gets a current 7.0.x either way; the lockfile change affects this repository's own development and CI. The rest of the lockfile movement is development tooling, including a chalk major version and a Node.js 22 floor on the test runner's own tree (see Dependencies).


🔧 Dependencies

Every entry is a lockfile-only update within the existing package.json range. The ranges still read ignore ^7.0.5, @cldmv/vitest-runner ^1.4.2, vitest ^5.0.0 and eslint ^10.11.0, and so on.

Runtime

  • ignore 7.0.10 → 7.0.12 (#138). Upstream's two patch releases drop a pattern that normalizes to nothing, and make trimming and unescaping of pattern whitespace run in linear time. They also fix handling of trailing spaces in directory patterns. The range allowed these versions before, and engines.node for the package (>=22.12.0) is unchanged.

Development

  • @cldmv/vitest-runner 1.5.1 → 1.5.3 (#138). This is the change with the widest effect. Version 1.5.2 moved the runner's own dependency chalk from 5.6.2 to 6.0.1, and 1.5.3 raised its engines.node from >=20.19.0 to >=22.12.0. In this lockfile chalk therefore moves from 5.6.2 to 6.0.1, a major version that requires Node.js 22 or later. fix-headers already requires Node.js >=22.12.0, so nothing here is newly excluded. Version 1.5.3 also fixes the runner's CommonJS entry, which now throws a clear ERR_REQUIRE_ESM error on a Node.js without require(esm), and relicenses the runner under Apache-2.0.
  • vitest 5.0.2 → 5.0.3 (#134), with @vitest/coverage-v8, @vitest/mocker and @vitest/spy at 5.0.3. vite 8.3.1 → 8.3.2, rolldown 1.2.11 → 1.2.12 (and its platform bindings) and @oxc-project/types 0.151.0 → 0.152.0 moved with them in the lockfile.
  • eslint 10.11.0 → 10.12.0 (#135).
  • globals 17.12.0 → 17.13.0 (#137).
  • @cldmv/eslint-plugin-jsonv 1.0.13 → 1.0.15, @cldmv/jsonv 1.1.1 → 1.1.3 and @cldmv/prettier-plugin-jsonv 1.1.0 → 1.1.3 (#138). These are the lint and format plugins for .jsonv files. The releases between these versions update test expectations and CI; this repository has no .jsonv files.
  • @types/node 26.6.3 → 26.6.4 (#138).
  • why-is-node-running 3.2.2 → 3.2.1, a transitive dependency of vitest. vitest 5.0.3 depends on exactly 3.2.1 where 5.0.2 allowed ^3.2.1, so the lockfile steps back to that version; it is a development-only package.

📚 Documentation


Upgrade notes

  • No breaking changes and no change to the fixHeaders API, the CLI, the header format or the declared dependency ranges: drop-in for v2.2.1.
  • The published package differs from 2.2.1 only in its version field. Installs resolve ignore from ^7.0.5 as before.
  • Contributors need Node.js 22.12 or later, which was already the repository's floor. Node.js 20 cannot install the development toolchain: @cldmv/vitest-runner 1.5.3 and chalk 6 both require Node.js 22.

... (truncated)

Commits

Updates @cldmv/jsonv from 1.1.3 to 1.1.5

Release notes

Sourced from @​cldmv/jsonv's releases.

v1.1.5

@cldmv/jsonv v1.1.5 Changelog

Release Date: October 2026 Release Type: Patch


Overview

Version 1.1.5 is a dev-dependency refresh. Nothing under src/, scripts/ or the published dist/ changed, and package.json differs from v1.1.4 only in its version field: every bump below is a lockfile re-resolution inside the existing ^ ranges. Every package that changed in package-lock.json is a development dependency, so the published package and its consumers are unaffected.

The one change that reaches beyond a patch bump is in the test toolchain. @cldmv/vitest-runner 1.5.3 raises its own Node.js floor from >=20.19.0 to >=22.12.0 and moves to chalk 6, which also needs Node.js 22. The repository's CI matrix already starts at 22.12.0 (the floor vitest 5 runs on), so CI is not affected; running npm test locally now needs Node.js 22.12.0 or later.


🔧 CI & tooling

  • The test runner @cldmv/vitest-runner 1.5.3 adds require() checks for its own CommonJS entry and fails with a clear ERR_REQUIRE_ESM message on Node.js without require(esm). It affects only how the runner loads, not how this repository's tests run: npm test (Vitest, then the node:test CommonJS entry checks) and npm run build:ci pass on the merged next branch.
  • @cldmv/eslint-plugin-jsonv 1.0.15 only updates that plugin's own expectations for @cldmv/jsonv 1.1.1 behavior; the lint rules this repository uses are unchanged.

📚 Documentation


🔧 Dependencies

All development-only. The lockfile entries are dev; none is a runtime or peer dependency, and package.json ranges are untouched.

  • @cldmv/vitest-runner 1.5.1 → 1.5.3 (#92). Its engines.node moves from >=20.19.0 to >=22.12.0, and its chalk dependency moves from ^5.4.1 to ^6.0.1. In the lockfile that replaces the runner's nested chalk 5.6.2 with a top-level chalk 6.0.1 (engines.node >=22).
  • @cldmv/eslint-plugin-jsonv 1.0.13 → 1.0.15 (#92). Its engines.node (^20.19.0 || ^22.13.0 || >=24) is unchanged.
  • @types/node 26.6.3 → 26.6.4 (#92).
  • vitest 5.0.2 → 5.0.3, with @vitest/coverage-v8, @vitest/mocker and @vitest/spy at 5.0.3 (#87). vitest 5.0.3 pins its why-is-node-running dependency to exactly 3.2.1, so that package resolves one patch version lower than before (3.2.2 → 3.2.1). vitest still requires Node.js ^22.12.0 || ^24.0.0 || >=26.0.0.
  • eslint 10.11.0 → 10.12.0 (#88).
  • globals 17.12.0 → 17.13.0 (#90).
  • Transitive tooling that moved with the Vitest update: vite 8.3.1 → 8.3.2, rolldown 1.2.11 → 1.2.12 (and its platform bindings) and @oxc-project/types 0.151.0 → 0.152.0.

Upgrade notes

  • No breaking changes, and no runtime code changed. It is a drop-in replacement for v1.1.4.
  • The package's engines field (>=18.0.0) and the Node.js requirement for require() (^20.19.0 or >=22.12.0) are unchanged.
  • For contributors: running the test suite locally needs Node.js 22.12.0 or later, the same floor vitest 5 has and the CI matrix already uses.

... (truncated)

Commits
  • de137e0 release: v1.1.5 - bump the patch group across 1 directory with 3 updates
  • 059f51f release: v1.1.4 - make require() a synchronous wrapper around the ESM…
  • See full diff in compare view

Updates @cldmv/prettier-plugin-jsonv from 1.1.3 to 1.1.4

Release notes

Sourced from @​cldmv/prettier-plugin-jsonv's releases.

v1.1.4

@cldmv/prettier-plugin-jsonv v1.1.4 Changelog

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


Overview

A dev-dependency release: @cldmv/fix-headers moves to 2.2.0 and @cldmv/configs to 1.2.4. The header pass was re-run for 2.1.4, and every header already matched what that version writes, so no file was restamped; the 2.2.0 and 1.2.4 bumps changed only package.json and the lockfile. No plugin code, published file or runtime dependency changed.


📚 Documentation

🔧 Dependencies

Both changes are to development dependencies. The runtime peerDependencies and the published package are unchanged.

  • @cldmv/fix-headers ^2.1.1 → ^2.2.0 (#51 took it to ^2.1.4, #54 to ^2.2.0). Version 2.1.4 no longer writes a JavaScript comment into JSON or Markdown files, processes every repeated --input, and never walks dependency folders such as node_modules. Version 2.2.0 makes the @Last modified by header tag follow content edits only, so a header-only rewrite keeps the recorded editor instead of replacing it. It requires Node.js >=22.12.0, the same floor as the rest of the development toolchain.
  • @cldmv/configs ^1.2.0 → ^1.2.4 (#54). It provides the shared fix-headers configuration that .configs/fix-headers.json extends. Version 1.2.4 turns off forceAuthorUpdate and forceLastModifiedAuthorUpdate (both were on in 1.2.0), so the shared configuration no longer overwrites the recorded author or last editor.
  • Despite its title, #51 (restamp file headers) changed only package.json and the lockfile. Neither it nor #54 restamped any header.

Upgrade notes

  • No runtime changes — drop-in for v1.1.3.

coverage

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

Avg: 100.0% · 5893750 · Node lts/*

... (truncated)

Commits
  • 7dab49b release: v1.1.4 - bump @​cldmv/fix-headers to 2.1.4 and restamp file…
  • See full diff in compare view

Updates @cldmv/vitest-runner from 1.5.3 to 1.5.4

Release notes

Sourced from @​cldmv/vitest-runner's releases.

v1.5.4

vitest-runner v1.5.4 Changelog

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


Overview

A dev-tooling dependency release with no change to the published package. Two development dependencies move forward, @cldmv/fix-headers (the tool that maintains the comment headers at the top of source, test, config and workflow files) and @cldmv/configs (the shared lint, format and header configuration), and the dev-only transitive brace-expansion is patched to 5.0.12.

Nothing under src/, tests/, bin/ or the build configuration changed, so dist/ and the CLI, the run() API and the CommonJS entry are identical to v1.5.3. The runtime dependency and peer ranges are untouched, and the only lockfile entries that moved are the three below. No file headers were restamped: both fix-headers steps and the configs bump re-ran fix:headers and changed no file.


🔧 Dependencies

All dev-only; none of them is installed by consumers of the package.

  • @cldmv/fix-headers ^2.1.2 → ^2.2.0 (locked 2.1.2 to 2.2.0), in two steps: 2.1.4 (#74) and 2.2.0 (#78). Version 2.1.4 never adds a JS comment header to JSON, Markdown or extension-less files and never walks into dependency folders. From 2.2.0 the @Last modified by tag follows content edits only, so a header-only rewrite keeps the recorded editor.
  • @cldmv/configs ^1.2.1 → ^1.2.4 (locked 1.2.1 to 1.2.4) (#78). The older shared fix-headers.json forced forceAuthorUpdate and forceLastModifiedAuthorUpdate on; version 1.2.4 sets both to false, so @Author is never rewritten and @Last modified by changes only on real content edits.
  • brace-expansion 5.0.9 → 5.0.12, an indirect dev dependency (pulled in through minimatch), updated by Dependabot's npm_and_yarn group (#76). Lockfile only; package.json does not list it.

📚 Documentation


Upgrade notes

  • No breaking changes and no change to what the package ships: a drop-in replacement for v1.5.3. The Node.js 22.12 floor introduced in v1.5.3 is unchanged.

coverage

Metric Coverage
Statements 99.4%
Branches 99.6%
Functions 100.0%
Lines 99.3%

Avg: 99.5% · 37726c2 · Node lts/*

... (truncated)

Commits

Updates @eslint/css from 2.0.0 to 2.0.1

Release notes

Sourced from @​eslint/css's releases.

css: v2.0.1

2.0.1 (2026-10-11)

Bug Fixes

  • allow additional properties in CSSLanguageOptions (#538) (471e568)
  • crash in no-important on non-standard important values (#541) (2985ad5)
  • handle var() and env() in no-invalid-at-rules (#570) (75050c3)
  • preserve keyframe selector casing in error messages (#571) (6589273)
  • preserve property casing in use-baseline messages (#573) (0f65765)
  • prevent crashes on [@supports](https://github.com/supports) queries in use-baseline (#576) (6ecf264)
  • recognize at-rule() feature queries in use-baseline (#533) (ba65596)
  • recognize CSS whitespace in named grid areas (#556) (ea5407d)
  • report each disallowed attribute location in selector-complexity (#580) (2bf2350)
  • support at-rules nested in [@page](https://github.com/page) and [@font-feature-values](https://github.com/font-feature-values) (#543) (12ec029)
  • update baseline data (bcd705e)
  • update baseline data (#561) (94d79a4)
  • update baseline data (#566) (9856c3b)
  • update baseline data (#579) (c60193b)
  • update baseline data (#585) (7a2dc06)
  • update baseline data (#589) (38ac3ad)
  • update dependency @​eslint/css-tree to ^4.1.1 (#568) (ae69b1a)
  • update eslint (#554) (33e7314)
Changelog

Sourced from @​eslint/css's changelog.

2.0.1 (2026-10-11)

Bug Fixes

  • allow additional properties in CSSLanguageOptions (#538) (471e568)
  • crash in no-important on non-standard important values (#541) (2985ad5)
  • handle var() and env() in no-invalid-at-rules (#570) (75050c3)
  • preserve keyframe selector casing in error messages (#571) (6589273)
  • preserve property casing in use-baseline messages (#573) (0f65765)
  • prevent crashes on [@supports](https://github.com/supports) queries in use-baseline (#576) (6ecf264)
  • recognize at-rule() feature queries in use-baseline (#533) (ba65596)
  • recognize CSS whitespace in named grid areas (#556) (ea5407d)
  • report each disallowed attribute location in selector-complexity (#580) (2bf2350)
  • support at-rules nested in [@page](https://github.com/page) and [@font-feature-values](https://github.com/font-feature-values) (#543) (12ec029)
  • update baseline data (bcd705e)
  • update baseline data (#561) (94d79a4)
  • update baseline data (#566) (9856c3b)
  • update baseline data (#579) (c60193b)
  • update baseline data (#585) (7a2dc06)
  • update baseline data (#589) (38ac3ad)
  • update dependency @​eslint/css-tree to ^4.1.1 (#568) (ae69b1a)
  • update eslint (#554) (33e7314)
Commits
  • c29255e chore: release 2.0.1 🚀 (#558)
  • 38ac3ad fix: update baseline data (#589)
  • 6ecf264 fix: prevent crashes on @supports queries in use-baseline (#576)
  • b774dbd chore: update dependency @​eslint/json to ^2.1.1 (#588)
  • 7a2dc06 fix: update baseline data (#585)
  • 2e80de0 docs: Update README sponsors
  • f6a4917 chore: update dependency prettier to v3.9.9 (#583)
  • 2bf2350 fix: report each disallowed attribute location in selector-complexity (#580)
  • 0f65765 fix: preserve property casing in use-baseline messages (#573)
  • c60193b fix: update baseline data (#579)
  • Additional commits viewable in compare view

Updates @eslint/json from 2.1.0 to 2.1.1

Release notes

Sourced from @​eslint/json's releases.

json: v2.1.1

2.1.1 (2026-10-06)

Bug Fixes

  • escape normalized keys in no-unnormalized-keys autofix (#283) (35790d4)
  • handle empty and whitespace-only JSON inputs (#259) (85ca99b)
  • preserve parsing error locations in Bun (#281) (bbaa18f)
  • update dependency @​eslint/plugin-kit to ^0.7.3 (#276) (780bfcd)
Changelog

Sourced from @​eslint/json's changelog.

2.1.1 (2026-10-06)

Bug Fixes

  • escape normalized keys in no-unnormalized-keys autofix (#283) (35790d4)
  • handle empty and whitespace-only JSON inputs (#259) (85ca99b)
  • preserve parsing error locations in Bun (#281) (bbaa18f)
  • update dependency @​eslint/plugin-kit to ^0.7.3 (#276) (780bfcd)
Commits
  • 412ad09 chore: release 2.1.1 🚀 (#278)
  • e7f8cbe chore: update dependency prettier to v3.9.9 (#289)
  • 812d486 docs: add missing Options section (#290)
  • a2b9af9 docs: Update README sponsors
  • c6af8f6 chore: update dependency prettier to v3.9.8 (#288)
  • 35790d4 fix: escape normalized keys in no-unnormalized-keys autofix (#283)
  • 7eb9cf3 docs: clarify JSON5 Infinity and NaN handling in no-unsafe-values (#279)
  • 85ca99b fix: handle empty and whitespace-only JSON inputs (#259)
  • 2cf7eb9 chore: update dependency prettier to v3.9.7 (#287)
  • 3285615 docs: Update README sponsors
  • Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 5.0.3 to 5.0.5

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.5

   🐞 Bug Fixes

    View changes on GitHub

v5.0.4

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates vitest from 5.0.3 to 5.0.5

Release notes

Sourced from vitest's releases.

v5.0.5

   🐞 Bug Fixes

Bumps the patch group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@cldmv/slothlet](https://github.com/CLDMV/slothlet) | `3.22.0` | `3.22.1` |
| [@cldmv/wisp](https://github.com/CLDMV/wisp) | `1.0.6` | `1.0.8` |
| [@cldmv/eslint-plugin-jsonv](https://github.com/CLDMV/jsonv-eslint-plugin-jsonv) | `1.0.15` | `1.0.17` |
| [@cldmv/fix-headers](https://github.com/CLDMV/fix-headers) | `2.2.0` | `2.2.2` |
| [@cldmv/jsonv](https://github.com/CLDMV/jsonv) | `1.1.3` | `1.1.5` |
| [@cldmv/prettier-plugin-jsonv](https://github.com/CLDMV/jsonv-prettier-plugin-jsonv) | `1.1.3` | `1.1.4` |
| [@cldmv/vitest-runner](https://github.com/CLDMV/vitest-runner) | `1.5.3` | `1.5.4` |
| [@eslint/css](https://github.com/eslint/css) | `2.0.0` | `2.0.1` |
| [@eslint/json](https://github.com/eslint/json) | `2.1.0` | `2.1.1` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.3` | `5.0.5` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.3` | `5.0.5` |



Updates `@cldmv/slothlet` from 3.22.0 to 3.22.1
- [Release notes](https://github.com/CLDMV/slothlet/releases)
- [Commits](https://github.com/CLDMV/slothlet/compare/@cldmv/slothlet-i18n@3.22.0...@cldmv/slothlet-i18n@3.22.1)

Updates `@cldmv/wisp` from 1.0.6 to 1.0.8
- [Release notes](https://github.com/CLDMV/wisp/releases)
- [Commits](CLDMV/wisp@v1.0.6...v1.0.8)

Updates `@cldmv/eslint-plugin-jsonv` from 1.0.15 to 1.0.17
- [Release notes](https://github.com/CLDMV/jsonv-eslint-plugin-jsonv/releases)
- [Commits](CLDMV/jsonv-eslint-plugin-jsonv@v1.0.15...v1.0.17)

Updates `@cldmv/fix-headers` from 2.2.0 to 2.2.2
- [Release notes](https://github.com/CLDMV/fix-headers/releases)
- [Commits](CLDMV/fix-headers@v2.2...v2.2.2)

Updates `@cldmv/jsonv` from 1.1.3 to 1.1.5
- [Release notes](https://github.com/CLDMV/jsonv/releases)
- [Changelog](https://github.com/CLDMV/jsonv/blob/master/CHANGELOG.md)
- [Commits](CLDMV/jsonv@v1.1.3...v1.1.5)

Updates `@cldmv/prettier-plugin-jsonv` from 1.1.3 to 1.1.4
- [Release notes](https://github.com/CLDMV/jsonv-prettier-plugin-jsonv/releases)
- [Commits](CLDMV/jsonv-prettier-plugin-jsonv@v1.1.3...v1.1.4)

Updates `@cldmv/vitest-runner` from 1.5.3 to 1.5.4
- [Release notes](https://github.com/CLDMV/vitest-runner/releases)
- [Commits](CLDMV/vitest-runner@v1.5.3...v1.5.4)

Updates `@eslint/css` from 2.0.0 to 2.0.1
- [Release notes](https://github.com/eslint/css/releases)
- [Changelog](https://github.com/eslint/css/blob/main/CHANGELOG.md)
- [Commits](eslint/css@css-v2.0.0...css-v2.0.1)

Updates `@eslint/json` from 2.1.0 to 2.1.1
- [Release notes](https://github.com/eslint/json/releases)
- [Changelog](https://github.com/eslint/json/blob/main/CHANGELOG.md)
- [Commits](eslint/json@json-v2.1.0...json-v2.1.1)

Updates `@vitest/coverage-v8` from 5.0.3 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/coverage-v8)

Updates `vitest` from 5.0.3 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/vitest)

---
updated-dependencies:
- dependency-name: "@cldmv/slothlet"
  dependency-version: 3.22.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/wisp"
  dependency-version: 1.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/eslint-plugin-jsonv"
  dependency-version: 1.0.17
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/fix-headers"
  dependency-version: 2.2.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/jsonv"
  dependency-version: 1.1.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/prettier-plugin-jsonv"
  dependency-version: 1.1.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@cldmv/vitest-runner"
  dependency-version: 1.5.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@eslint/css"
  dependency-version: 2.0.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@eslint/json"
  dependency-version: 2.1.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
- dependency-name: vitest
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@cldmv-bot cldmv-bot Bot added type: dependencies Relates to dependency updates, version bumps, or package management and removed dependencies labels Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants