[aversini]

Automated non-major dependency bump (deps-train).

package.json

• @versini/dev-dependencies-common 14.0.7 → 14.0.8
• pnpm 11.22.0 → 11.23.0

---

What changed

@versini/dev-dependencies-common 14.0.7 → 14.0.8

dev-dependencies-common: v14.0.8

14.0.8 (2026-08-24)

Bug Fixes

• bump non-breaking dependencies to latest (#908) (5d1fd81)

compare 14.0.7…14.0.8 · npm

pnpm 11.22.0 → 11.23.0

pnpm 11.23

Minor Changes

• pnpm config get and pnpm config list now show the settings pnpm acts on under their documented names:

  • registries shows the registries pnpm resolves from, merged across every source (.npmrc, pnpm-workspace.yaml, the global config, CLI flags), in the shape the setting is written in: keyed by registry URL, with the default registry declared as the bare @ scope. Built-in routes are included — the @jsr scope and the npmjs and gh prefixes — unless pointed elsewhere. Previously pnpm config get registries printed undefined.
  • update and audit show the effective sections, whichever spelling set them. The deprecated internal spellings (updateConfig, auditConfig, auditLevel) are no longer listed.
  • catalogs shows the complete resolved catalog set — the singular catalog block is its default entry — whichever spelling declared it.
  • The registry and @scope:registry entries show the merged routes rather than raw .npmrc values, so they always agree with the registries view.

• Settings that no supported pnpm version recognizes get their own warning. A key in the global config file that this version of pnpm does not read is no longer reported with advice to move it to a project-level pnpm-workspace.yaml (where it would be ignored too); the warning now says the setting is not recognized by this version of pnpm, names the pnpm version that does read it when there is one (for example, globalShims is a pnpm

…notes truncated.

compare 11.22.0…11.23.0 · npm