Agent skill
dependency-updates
Esposter dependency update process — all versions in pnpm-workspace.yaml catalog, caret prefix rules, pinned packages (nuxt, h3, ctix), and tracked open issues. Apply when updating package versions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/dependency-updates
SKILL.md
Dependency Updates
All version numbers live in the catalog: section of pnpm-workspace.yaml at the repo root. Individual package.json files reference them with catalog: — never edit version numbers there.
Process
-
Check what's outdated (run from repo root):
pnpm outdated -r -
Update versions in
pnpm-workspace.yaml— all non-pinned packages must have a^caret prefix. -
Refresh the lockfile manually — run
pnpm refresh:lockfilefrom the repo root yourself after updating versions.
Pinned packages (do not update)
nuxt— no^, manually managed (infrastructure, coordinates withh3and Nuxt modules).h3— skip major/RC bumps; only update minor/patch within the current major.ctix— pinned (no^) due to open issue https://github.com/imjuni/ctix/issues/192.survey-core,survey-vue3-ui,survey-creator-core,survey-creator-vue— pinned to2.5.15(no^);2.5.16broke type declarations forsurvey-creator-core/themes.
Tracked issues (update normally, but watch these)
oxlint— has^; open issue https://github.com/oxc-project/oxc/issues/13204.ajv,ajv-errors,ajv-formats,ajv-i18n,debug— required by@koumoul/vjsf; tracked at https://github.com/json-layout/json-layout/issues/5.db:runscript — workaround for https://github.com/drizzle-team/drizzle-orm/issues/1228.
Caret rules
Every catalog entry must have ^ except pinned packages listed above. If an entry is missing ^ with no entry in the pinned list above, add it when updating.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?