update-crates

Update Rust workspace crate dependencies while preserving lockfile and manifest pins.

Updated Aug 23, 2026

Search Tags:#dependencies #workspace #rust #semver #cargo #lockfile

Ready to run

npx skills add https://github.com/neon-law-foundation/navigator --skill update-crates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-crates
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/update-crates
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill update-crates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers update Rust workspace dependencies without accidentally breaking version pins, toolchain constraints, or the project’s release discipline.

Core Features & Use Cases

Lockfile Refreshes: Updates Cargo.lock with semver-compatible dependency changes while keeping manifests unchanged.
Manifest Upgrades: Revises Cargo.toml version requirements when a deliberate major bump is needed.
Safety Guardrails: Preserves the pinned Rust 1.95.0 toolchain, respects existing pin comments, and requires standard verification before merging.

Quick Start

Ask the AI to update the workspace Rust crate dependencies while preserving the pinned toolchain and existing version constraints.

Frequently Asked Questions about update-crates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update Rust crate dependencies in a Cargo workspace without breaking the lockfile?▼

To update Rust crate dependencies without breaking the lockfile, you can refresh Cargo.lock with semver-compatible changes while keeping manifests unchanged. This preserves existing pins and requires formatting, clippy, and tests to pass.

Can I upgrade a Cargo.toml dependency to a new major version without losing my pinned Rust toolchain?▼

You can upgrade Cargo.toml major versions while preserving the pinned Rust toolchain. The update process respects version caps, comments, and toolchain constraints, ensuring deliberate major bumps do not override existing environment pins.

What is the best way to do semver-compatible dependency updates across a Rust workspace?▼

The best way to perform semver-compatible dependency updates across a Rust workspace is to refresh the lockfile while respecting existing manifest pins and version caps. This ensures workspace tests and clippy checks verify compatibility.

Does updating workspace dependencies run formatting and clippy checks before merging?▼

Updating workspace dependencies does run formatting and clippy checks before merging. Standard verification steps are required to ensure dependency changes do not introduce formatting violations or lint errors into the Rust workspace.

Why does my Cargo lockfile update break my pinned Rust 1.95.0 toolchain constraint?▼

A Cargo lockfile update might break a pinned Rust 1.95.0 toolchain constraint if version caps are ignored. Safe dependency maintenance preserves this exact toolchain version while applying semver-compatible updates.

When do I need to update Cargo.toml version requirements instead of just refreshing the lockfile?▼

You need to update Cargo.toml version requirements instead of just refreshing the lockfile when a deliberate major-version upgrade is required. Lockfile refreshes only handle semver-compatible dependency changes without altering manifest pins.