AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Bump Deps

skill-fedoroff-vlad-agent-skills-bump-deps · by fedoroff-vlad

>

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-fedoroff-vlad-agent-skills-bump-deps

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fedoroff-vlad-agent-skills-bump-deps)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Bump Deps? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

bump-deps — one version, propagated to every pin

A dependency version usually lives in more than one place. Bump the source of truth, then chase every pin — a half-bumped dependency is drift that compiles.

Procedure

  1. Identify the SSOT: the manifest that declares the version — e.g.

pom.xml dependency management, pyproject.toml, package.json. Bump there.

  1. Sync the lockfile: regenerate the lock so it matches (uv lock,

npm install, etc.). Lockfile and manifest must move together — CI likely runs --locked / --frozen and will fail otherwise.

  1. Chase pinned references: grep for the old version string in scripts,

Dockerfiles, docs, .env examples, README badges — bump each. Consult .skills/change-map.yaml if a "new dependency" coupling is listed.

  1. Respect load-bearing pins: some pins are intentional (a BOM, a

Testcontainers version). Do not "upgrade" those blindly — confirm before touching a pin the project marks as deliberate.

  1. Rebuild + revalidate: run the build and the relevant tests / golden lane.

A dependency bump is not done until the suite is green.

  1. Report breaking changes: if the bump pulled a breaking transitive change,

surface it — do not silently paper over it.

Output

Old → new version, every file touched, build/test result. If the build breaks, report the failing assertion — do not leave a half-applied bump.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.