pac-cli-update

Automates PAC CLI and cli-wrapper version bumps across two PRs on main and release/stable branches.

298|70|Updated Nov 4, 2020
One-click install
npx skills add https://github.com/microsoft/powerplatform-build-tools --skill pac-cli-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pac-cli-update
Source: https://github.com/microsoft/powerplatform-build-tools/tree/main/.claude/skills/pac-cli-update
Command: npx skills add https://github.com/microsoft/powerplatform-build-tools --skill pac-cli-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the PAC CLI version bump workflow and ensures the repository creates two PRs: one on main and one on release/stable, for both the PAC CLI binary and the cli-wrapper package.

Core Features & Use Cases

  • Automated version bumps for the Microsoft.PowerApps.CLI and Microsoft.PowerApps.CLI.Core.linux-x64 packages.
  • Dual-branch release workflow: two PRs per update (main and release/stable).
  • Release process integration: updates to nuget.json and extension/overview.md.

Quick Start

Create two PRs updating PAC CLI and cli-wrapper to the new version on the main and release/stable branches.

Frequently Asked Questions about pac-cli-update

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

FAQPage Schema
How do I automate a PAC CLI version bump across main and release branches?

You can automate the PAC CLI version bump by generating two pull requests that update Microsoft.PowerApps.CLI packages across main and release/stable branches. This includes synchronizing nuget.json and extension/overview.md changes to ensure consistent updates.

What is the dual PR release workflow for PAC CLI and cli-wrapper updates?

The dual PR workflow creates two pull requests per update: one on the main branch and one on release/stable. This ensures synchronized nuget.json and extension/overview.md changes for both the PAC CLI binary and cli-wrapper package with proper CI verification.

Can I use this automated bump process for repositories without a release/stable branch?

No, this process applies to repositories using a main and release/stable branching model. It requires this dual-branch structure to create the two synchronized PRs needed for publishing consistent PAC CLI and cli-wrapper updates.

Which files need to be modified when updating Microsoft.PowerApps.CLI packages?

Updating Microsoft.PowerApps.CLI packages requires modifying nuget.json and extension/overview.md to reflect the new version. These file changes must be included in both the main and release/stable branch pull requests to complete the release workflow.

Does the PAC CLI bump workflow include CI verification and validation steps?

Yes, the PAC CLI bump workflow ensures validation steps, CI verification, and release workflow steps are followed to publish consistent updates. This guarantees both the binary and cli-wrapper package updates pass necessary checks before merging.