release-management

Manage semantic versioning, changelog updates, and Git tagging for Pact 5 contracts and TypeScript packages.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill release-management-pact-community-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/release-management
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill release-management-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Versioning, tagging, and release notes management for Pact 5 smart contracts and TypeScript packages. It provides a repeatable, auditable process to apply semantic versioning, generate changelog entries, and surface release tasks.

Core Features & Use Cases

  • Enforce semantic versioning across contracts and packages, ensuring breaking changes are clearly indicated.
  • Generate and synchronize CHANGELOG entries with Git tags and release notes for all artifacts.
  • Follow a repeatable release checklist to validate changes, document migrations, and publish with confidence.

Quick Start

Create a new release by incrementing the version, updating the changelog, and tagging the release.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I manage semantic versioning and changelog updates for Pact 5 contracts?

To manage semantic versioning for Pact 5 contracts, apply a repeatable workflow that enforces MAJOR.MINOR.PATCH formats, updates changelog entries, and handles Git tagging to ensure consistency across packages and environments.

What is the best way to generate release notes and apply Git tags for TypeScript packages?

Generating release notes and applying Git tags for TypeScript packages involves following a structured release checklist that synchronizes changelog entries with version increments and tags, while optionally including migration notes for breaking changes.

How do I indicate breaking changes when releasing new Pact smart contract versions?

To indicate breaking changes in Pact smart contract versions, the release process enforces semantic versioning rules that clearly bump the MAJOR version, ensuring protocol changes are explicitly documented across all affected environments.

Does this release management workflow support both library releases and protocol changes?

Yes, the release management workflow applies consistently across contract updates, library releases, and protocol changes, ensuring that semantic versioning and changelog synchronization are handled uniformly across different artifact types.

Can I use this process to document migration notes for breaking contract updates?

Yes, you can document migration notes during the release process. The workflow includes an optional step for preparing migration notes within the changelog to validate changes and publish with confidence.