[aversini]

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

package.json

• pnpm 12.17.0 → 12.18.0

packages/static-server/package.json

• @fastify/static 10.1.9 → 10.1.10

Transitive refresh (pnpm update) — 2 package(s) moved

Show transitive changes

• @babel/helper-string-parser 7.29.11 → 7.29.13
• @babel/parser 7.29.12 → 7.29.13

---

What changed

pnpm 12.17.0 → 12.18.0

pnpm 12.18

pnpm 12.18.0 packs, publishes, and installs packages with platform variants on pnpr registries. It also adds per-skill approval of agent skills and pnpm store add for offline installs from downloaded tarballs. Repeat installs and verifyDepsBeforeRun no longer read the package.json of unchanged workspace projects. The release fixes several peer dependency resolution bugs too.

Minor Changes

Agent skills

• pnpm now names the link to a dependency's agent skill after the skill alone. A skill that the @acme/kit package ships in skills/auth/ is linked as .claude/skills/auth, not .claude/skills/pnpm-@acme+kit-auth. The next install replaces links with the old names. pnpm lists the linked skills in a # pnpm block of each agent skill directory's .gitignore #17455.

  When two approved packages ship a skill of the same name, or the name is already taken in an agent skill directory, pnpm links the skill as pnpm-<package>-<skill>. Before, the install failed.

• pnpm approve now asks which agent skills to link when a package ships more than one. pnpm records the chosen skills as a list, such as permissions.<pkg>.skills: [guide, migrate], and does not offer the other skills for approval again. The first time a project approves a skill, pnpm approve also asks which agent directories to link skills into, and records the answer under skills.dirs.

• pnpm links agent skills nested in category d

…notes truncated.

compare 12.17.0…12.18.0 · npm

@fastify/static 10.1.9 → 10.1.10

v10.1.10

What's Changed

• fix: use @fastify/error for forbidden path errors by @SkySails in fix: use @fastify/error for forbidden path errors fastify/fastify-static#624
  The 403 response for forbidden paths now includes code: "FST_STATIC_FORBIDDEN_PATH"; the error no longer has a status property, use statusCode.

New Contributors

• @SkySails made their first contribution in fix: use @fastify/error for forbidden path errors fastify/fastify-static#624

Full Changelog: fastify/fastify-static@v10.1.9...v10.1.10

compare 10.1.9…10.1.10 · npm