update-azure-deps

Update Azure SDK Go dependencies with a major-aware upgrade plan.

407|38|Updated Aug 16, 2022
One-click install
npx skills add https://github.com/mondoohq/mql --skill update-azure-deps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-azure-deps
Source: https://github.com/mondoohq/mql/tree/main/.claude/skills/update-azure-deps
Command: npx skills add https://github.com/mondoohq/mql --skill update-azure-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It eliminates the slow and error-prone process of manually bumping Azure SDK Go dependencies, auditing breaking changes, and updating call sites after major version upgrades.

Core Features & Use Cases

  • Stable-major dependency probing: Scans a provider's go.mod for github.com/Azure and github.com/AzureAD dependencies and identifies latest stable-major upgrades while separately flagging beta-only majors for user decision.
  • Changelog-based breaking change auditing: For every major-crossing upgrade, fetches and surfaces CHANGELOG sections so you can review breaking changes that may not appear as compile errors.
  • Automated upgrade workflow with targeted patch guidance: Provides a structured process to update go.mod, resolve imports/version paths, run go mod tidy, and validate with build/vet/test steps before you share diffs.

Quick Start

Run the Azure dependency probe for the provider go.mod at providers/azure/go.mod and use the printed UP rows to guide stable-only major upgrades.

Frequently Asked Questions about update-azure-deps

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

FAQPage Schema
How do I safely upgrade Azure SDK dependencies in a Go provider without breaking the build?

Upgrade Azure SDK Go dependencies by probing proxy.golang.org for latest stable-major versions, auditing crossed-major CHANGELOG breaking changes, updating call sites, and enforcing build, vet, and test validation after go.mod updates.

What is the best way to audit breaking changes when bumping major versions of github.com/Azure Go modules?

Audit breaking changes by fetching and reviewing CHANGELOG sections for every crossed-major Azure SDK upgrade, identifying breaking changes that may not appear as compile errors before updating call sites and running go mod tidy.

Why does go mod tidy fail when upgrading AzureAD Go modules with uppercase letters?

Upgrading AzureAD Go modules with uppercase paths requires !-encoding for proxy.golang.org probing to correctly discover latest stable-major versions and generate a major-aware upgrade plan.

Can I automatically update beta-only major versions of Azure SDK Go dependencies?

Beta-only major versions of Azure SDK Go dependencies are flagged separately for user decision rather than automatically upgraded, ensuring the upgrade plan targets safe stable-major bumps for code changes.

How do I resolve import path changes after crossing a major version in an Azure SDK Go module?

Resolve import path changes by updating go.mod, resolving imports and version paths at call sites, running go mod tidy, and validating with build, vet, and test steps before sharing diffs.

Does this dependency upgrade process work with all github.com/Azure and AzureAD Go modules?

The dependency upgrade process works by scanning a provider go.mod for github.com/Azure and github.com/AzureAD dependencies, identifying latest stable-major upgrades while separately flagging beta-only majors for user decision.