hotfix-release

Publish npm package hotfixes from Azure TypeSpec release branches with validation and backmerges.

27|86|Updated Nov 1, 2023
One-click install
npx skills add https://github.com/Azure/typespec-azure --skill hotfix-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix-release
Source: https://github.com/Azure/typespec-azure/tree/main/.github/skills/hotfix-release
Command: npx skills add https://github.com/Azure/typespec-azure --skill hotfix-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides maintainers through the complex process of publishing hotfix releases from existing release branches while preventing common release mistakes and ensuring changes reach the correct targets.

Core Features & Use Cases

  • Hotfix Release Workflow: Provides an ordered procedure for preparing branches, bumping package versions, creating pull requests, and publishing patched packages.
  • Release Validation: Ensures the correct release branch, targeted packages, version changes, and submodule state are verified before merging.
  • Use Case: Help an Azure TypeSpec maintainer publish a patch update for one or more npm packages from a release branch and complete the required backmerge process.

Quick Start

Use the hotfix-release skill to publish a patch release for the specified packages from an existing release branch.

Frequently Asked Questions about hotfix-release

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

FAQPage Schema
How do I publish a hotfix release from an existing git release branch?

To publish a hotfix release, you must validate the existing git release branch, bump the targeted package versions, handle submodules, pass CI checks, and complete npm publishing followed by a backmerge workflow.

What is the correct versioning workflow for npm package patch releases?

The correct versioning workflow for npm package patch releases involves validating the release branch, applying validated package version bumps, ensuring submodule state is correct, and executing the npm publishing procedure.

How does a backmerge workflow work when publishing hotfix packages?

A backmerge workflow ensures that changes merged into the release branch for the hotfix package are propagated back to the main branch, maintaining codebase consistency after the npm package patch release is published.

Can I use this hotfix workflow for Azure TypeSpec package maintenance?

Yes, this hotfix release workflow is specifically designed for Azure TypeSpec package maintenance scenarios, guiding maintainers through patch releases, release branch validation, pull requests, and backmerges.

What validations are required before merging a hotfix pull request?

Before merging a hotfix pull request, you must verify the correct release branch, targeted packages, version changes, and submodule state, ensuring all CI checks pass to prevent common release mistakes.

When should I use a dedicated hotfix release workflow instead of a standard release?

You should use a dedicated hotfix release workflow when you need to publish patch updates for existing npm packages from a release branch, ensuring validated version updates and proper backmerges without disrupting main branch development.