package-updater-update-package

Update one package

Move one named package to a target version wherever it is pinned, with a body that says what the release means for each repository it lands in.

Use the package-updater-updating-packages skill for the phase structure, and its references: references/repo-scope.md, references/ecosystems.md, references/commit-conventions.md, references/upstream-links.md, and references/follow-ups.md.

For a full sweep, use the package-updater-update skill. For a runtime or toolchain pin, use the package-updater-update-toolchain skill.

User arguments: $ARGUMENTS

Context

Repository — run this command and read the output:

git remote get-url origin 2>/dev/null || echo "(not a git repository)"

Default branch — run this command and read the output:

git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo "(unknown)"

Manifests that could pin it — run this command and read the output:

out=$(git ls-files -- 'pyproject.toml' '**/pyproject.toml' 'requirements*.txt' 'package.json' '**/package.json' 'Cargo.toml' 'go.mod' 2>/dev/null | grep -v node_modules | head -30); if [ -n "$out" ]; then echo "$out"; else echo "(none found)"; fi

Cooldown configuration — run this command and read the output:

out=$({ grep -hi 'minimumReleaseAge\|min-release-age' pnpm-workspace.yaml .npmrc; grep -hi 'exclude-newer' uv.toml pyproject.toml "${UV_CONFIG_FILE:-$HOME/.config/uv/uv.toml}"; } 2>/dev/null); if [ -n "$out" ]; then echo "$out"; else echo "(no cooldown configured)"; fi

Procedure

1. Resolve the target and confirm it exists

If the user named a version, use it. Otherwise take the latest stable release. Either way confirm it is published and record its publication timestamp — you need it to reason about the cooldown, and a version written before it is confirmed to exist is the expensive failure this ordering prevents.

If the cooldown currently hides it, say when it becomes visible and stop rather than exempting it. Exempt only when the release is needed now, and then per the exemption protocol in the ecosystems reference: narrow, annotated, its own commit, reverted when the block lapses.