update-dependencies

Update Go module dependencies for DCP executables and regenerate code.

183|18|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/microsoft/dcp --skill update-dependencies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-dependencies
Source: https://github.com/microsoft/dcp/tree/main/.agents/skills/update-dependencies
Command: npx skills add https://github.com/microsoft/dcp --skill update-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update packages that DCP executables depend on to keep them in sync with upstream Tilt and shared components, reducing drift and integration issues.

Core Features & Use Cases

  • Coordinate dependency updates across Tilt and Kubernetes-related packages to ensure parity.
  • Automate the flow from updating go.mod versions to regenerating code and validating builds.
  • Use at the start of a development cycle to refresh dependencies before a PR merge.

Quick Start

Run the update-dependencies skill to refresh DCP's Go module versions and regenerate code.

Frequently Asked Questions about update-dependencies

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

FAQPage Schema
How do I update Go module dependencies for DCP executables?

To update Go module dependencies for DCP executables, use an automated workflow that refreshes tilt-apiserver, aligns Kubernetes packages, updates direct dependencies, and regenerates code with make generate while tidying modules and validating builds.

When should I refresh DCP dependencies and align Kubernetes-related packages?

You should refresh DCP dependencies and align Kubernetes-related packages at the start of a development cycle to reduce drift and prevent integration issues before a PR merge.

What is the best way to keep tilt-apiserver dependencies in sync with shared components?

Keeping tilt-apiserver dependencies in sync involves updating to the latest release first, then aligning Kubernetes-related dependencies across DCP and tilt-apiserver to ensure parity and propagate updates.

Does updating go.mod versions automatically regenerate code and validate builds?

Yes, updating go.mod versions triggers a workflow that regenerates code using make generate, tidies Go modules, and validates builds to ensure the dependency updates do not break the project.

Why does updating tilt-apiserver require aligning Kubernetes-related dependencies across DCP?

Updating tilt-apiserver requires aligning Kubernetes-related dependencies across DCP because shared components must maintain parity with upstream Tilt packages, preventing drift and integration failures.