dependency-update

Update NuGet dependency versions in Directory.Packages.props via Azure DevOps mirroring.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/microsoft/aspire --skill dependency-update-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-update
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/dependency-update
Command: npx skills add https://github.com/microsoft/aspire --skill dependency-update-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Azure.Identity, Microsoft.Azure.Pipelines.WebApi, Microsoft.TeamFoundationServer.Client, Microsoft.VisualStudio.Services.Client, Microsoft.VisualStudio.Services.OAuth, Azure.Core.

What problem does it solve?

This Skill eliminates the manual and error-prone process of updating external NuGet dependencies in a repo that cannot consume them directly from nuget.org, by automating mirroring through an internal Azure DevOps pipeline. It helps ensure updated versions are mirrored via dotnet-migrate-package and that the changes are consistently reflected in Directory.Packages.props.

Core Features & Use Cases

  • Find current dependency versions in Directory.Packages.props and (when needed) eng/Versions.props for MSBuild-managed version properties.
  • Discover latest available versions from nuget.org and produce a recommendation summary (including stable vs pre-release behavior).
  • Mirror missing packages via Azure DevOps by triggering dotnet-migrate-package (pipeline ID 931) and monitoring completion before continuing.
  • Update central package versions in Directory.Packages.props after successful mirroring, and then guide a build verification.

Quick Start

Ask to update a dependency by saying: update Hex1b to the latest stable version, mirror it into the internal feeds, update Directory.Packages.props, and verify the build.

Frequently Asked Questions about dependency-update

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

FAQPage Schema
How do I update external NuGet dependencies in a repo that blocks direct nuget.org access?

Updating external NuGet dependencies without direct access requires mirroring them through an internal Azure DevOps pipeline. This ensures packages are safely imported before modifying central package management files.

How does central package management work when mirroring NuGet updates through Azure DevOps?

Central package management handles NuGet updates by triggering the dotnet-migrate-package pipeline in Azure DevOps to mirror missing versions. After pipeline completion, updated versions are applied to the Directory.Packages.props file.

Can I discover the latest stable and pre-release NuGet versions before mirroring?

Yes, you can discover the latest stable and pre-release candidates from nuget.org. The process generates a recommendation summary to help you select target versions before triggering the Azure DevOps mirroring pipeline.

What is the best way to handle bulk NuGet dependency updates in Azure DevOps?

The best way to handle bulk NuGet updates is to select the package scope and target versions, ask for confirmation, trigger the dotnet-migrate-package pipeline, and monitor its completion before editing central package versions.

Does updating Directory.Packages.props also check eng/Versions.props for MSBuild properties?

Yes, updating Directory.Packages.props also checks eng/Versions.props when needed. This ensures MSBuild-managed version properties are correctly identified and updated alongside central package management configurations.