bump-dependency

Automate dependency pin updates and verify CI workflows in GPU projects.

852|445|Updated May 21, 2025
One-click install
npx skills add https://github.com/NVIDIA-NeMo/Megatron-Bridge --skill bump-dependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-dependency
Source: https://github.com/NVIDIA-NeMo/Megatron-Bridge/tree/main/skills/bump-dependency
Command: npx skills add https://github.com/NVIDIA-NeMo/Megatron-Bridge --skill bump-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Managing dependency upgrades in complex projects can cause delays and integration issues, requiring careful coordination and testing.

Core Features & Use Cases

  • Automates dependency bump workflows: Enables seamless updating of pinned dependencies like TransformerEngine or Megatron-LM.
  • Ensures CI stability: Integrates with CI workflows to monitor, quarantine, and retest flaky or failing dependency updates before merging.
  • Use Case: When updating the TransformerEngine pointer in pyproject.toml, use this Skill to create a PR, trigger CI, monitor the build, quarantine flakes, and automatically re-run until stable.

Quick Start

Use the bump-dependency skill to update the transformer-engine dependency in pyproject.toml and monitor the CI until the workflow passes successfully.

Frequently Asked Questions about bump-dependency

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

FAQPage Schema
How do I automate dependency updates for pinned packages like TransformerEngine in pyproject.toml?

Automating dependency updates for pinned packages involves creating a pull request to modify configuration files, triggering CI workflows, and monitoring the build to ensure the new dependency versions integrate reliably before merging.

What is the best way to manage submodule revisions and relock dependencies in GPU-dependent AI projects?

Managing submodule revisions and relocking dependencies requires updating the pinned pointers in your configuration files, running adequate tests via CI workflows, and verifying stability before the changes are merged into the main branch.

Can I use CI workflows to quarantine and retest flaky dependency bumps?

Yes, you can use CI workflows to quarantine flaky or failing dependency updates, automatically re-running the tests until the build becomes stable and ensuring reliable CI/CD integration before merging.

Does automated dependency bump verification work with Megatron-LM and other complex AI project dependencies?

Automated dependency bump verification works with complex AI project dependencies like Megatron-LM by monitoring the CI workflow, quarantining flakes, and ensuring dependencies are relocked and adequately tested before merging.

Why does updating pinned dependencies in configuration files cause CI instability?

Updating pinned dependencies causes CI instability because new package versions may introduce breaking changes or integration issues, requiring careful coordination, build monitoring, and retesting to ensure reliable CI/CD integration.