create-release

Automate NuGet package release planning and execution in GitHub repositories.

Updated Sep 18, 2020
One-click install
npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill create-release-bitpantry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-release
Source: https://github.com/bitpantry/BitPantry.CommandLine/tree/main/.github/skills/create-release
Command: npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill create-release-bitpantry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates and centralizes the process of planning, executing, and managing NuGet package releases, ensuring a standardized and efficient release workflow.

Core Features & Use Cases

  • Release Planning: Identifies changed packages, determines version increments, and presents a release plan for user confirmation.
  • Execution: Executes the release procedure, including version bumping, building, testing, tagging, and pushing.
  • Post-Push Bookkeeping: Labels PRs and issues with release tags, updates project fields, and confirms the completion of the release.
  • Use Case: Ideal for .NET developers who want to automate and simplify the release of NuGet packages within their projects.

Quick Start

Execute the create-release skill to plan and initiate a release for your NuGet packages.

Frequently Asked Questions about create-release

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

FAQPage Schema
How do I automate NuGet package releases in GitHub repositories?

Automating NuGet package releases involves coordinating Git and GitHub CLI commands to execute version bumping, building, testing, tagging, and pushing. This Skill manages the complete lifecycle, ensuring semantic versioning adherence and standardized release workflows.

What is the process for planning a NuGet package release?

Planning a NuGet package release involves identifying changed packages and determining version increments based on semantic versioning. The Skill generates a release plan for user confirmation before executing any version bumping, building, or tagging procedures.

Do I need GitHub CLI installed to automate NuGet package versioning?

Yes, GitHub CLI and Git are required dependencies. You must have access to Git repositories and the ability to execute GitHub CLI commands to automate NuGet package releases, apply labels to issues, and update project fields.

Can I use release automation to label PRs and issues with release tags?

Yes, post-push bookkeeping automatically labels PRs and issues with release tags. It updates project fields and confirms release completion within GitHub, ensuring tracking is maintained after NuGet packages are pushed.

Does this release automation enforce semantic versioning for NuGet packages?

Yes, the Skill ensures semantic versioning adherence during NuGet package releases. It identifies changed packages, calculates the correct version increment, and presents the plan for confirmation before executing the version bump.