deps-update

Update Python dependencies with uv and regenerate lockfiles.

71|88|Updated Nov 8, 2023
One-click install
npx skills add https://github.com/openshift/lightspeed-service --skill deps-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deps-update
Source: https://github.com/openshift/lightspeed-service/tree/main/.cursor/skills/deps-update
Command: npx skills add https://github.com/openshift/lightspeed-service --skill deps-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependency drift and breaking changes in Python projects slow development. This skill updates dependencies to the latest compatible versions, regenerates lockfiles, and verifies that the project builds and tests pass.

Core Features & Use Cases

  • Bump dependencies to latest compatible versions using uv and update lock files.
  • Regenerate the pinned requirements.txt with hashes for reproducible builds.
  • Run lint and unit/integration tests to catch breakages and apply fixes.

Quick Start

Run the deps-update skill to refresh dependencies, rebuild the lock, and run the verification suite.

Frequently Asked Questions about deps-update

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

FAQPage Schema
How do I update Python dependencies and regenerate a lockfile using uv?

To update Python dependencies using uv, you bump packages to their latest compatible versions and regenerate the lockfile. This process also rebuilds the pinned requirements.txt with hashes to ensure reproducible builds across environments.

What is the best way to safely bump Python packages without breaking tests?

Safely bumping Python packages requires updating dependencies to compatible versions, regenerating lockfiles, and running lint and test suites. This verifies project integrity by catching and addressing breakages immediately after the dependency update.

Does this dependency update process support both single-package bumps and full upgrades?

Yes, the dependency update process supports both single-package bumps and full project upgrades. After updating the targeted dependencies, it regenerates the lockfile and runs validation checks to ensure the codebase remains stable.

How do I automate dependency drift resolution in a Python CI pipeline?

Automating dependency drift resolution in a Python CI pipeline involves end-to-end automation of bumping dependencies, locking versions, and validating the codebase. It updates outdated packages, regenerates lockfiles with hashes, and runs lint and tests automatically.

Why do I need to regenerate lockfiles with hashes when updating Python dependencies?

Regenerating lockfiles with hashes when updating Python dependencies ensures reproducible builds. Hashes pin the exact package versions and validate their integrity, preventing unexpected breaking changes or security issues from compromised or mismatched dependencies.

What happens if linting or tests fail after a Python dependency update?

When linting or tests fail after a Python dependency update, the process includes applying fixes to resolve the breakages. This end-to-end validation ensures the codebase builds successfully and tests pass with the newly bumped dependency versions.