Read Order

Start with AGENTS.md for the end-to-end workflow.
Run the main helper once at the start of the upgrade: node .agents/skills/pnpm-upgrade-package/scripts/check-release-age-window.mjs <package> [targetVersion]

Apply This Skill

Ask for the package name if the user did not provide one.
Ask for the target version if the user did not provide one.
Run the main helper once as the first analysis step and use that single output for scope, exclusion decisions, and the final bump.
If the target package is not directly declared anywhere, run pnpm why -r <package> to find which direct dependency brings it in, then inspect whether the current top-level parent already allows the requested transitive version via its dependency range.
If the current parent range already covers the requested transitive version, prefer a lockfile refresh / reinstall path over bumping the parent manifest.

Use this skill for interactive dependency bumps in Langfuse.

Start with AGENTS.md for the end-to-end workflow.
Run the main helper once at the start of the upgrade: node .agents/skills/pnpm-upgrade-package/scripts/check-release-age-window.mjs <package> [targetVersion]

Ask for the package name if the user did not provide one.
Ask for the target version if the user did not provide one.
Run the main helper once as the first analysis step and use that single output for scope, exclusion decisions, and the final bump.
If the target package is not directly declared anywhere, run pnpm why -r <package> to find which direct dependency brings it in, then inspect whether the current top-level parent already allows the requested transitive version via its dependency range.
If the current parent range already covers the requested transitive version, prefer a lockfile refresh / reinstall path over bumping the parent manifest.