release

Automate end-to-end release management for Plain packages in monorepos.

1.0k|27|Updated Mar 22, 2023
One-click install
npx skills add https://github.com/dropseed/plain --skill release-dropseed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/dropseed/plain/tree/main/.claude/skills/release
Command: npx skills add https://github.com/dropseed/plain --skill release-dropseed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Releasing Plain packages can be error-prone and time-consuming when synchronizing version bumps, changelogs, and Git tagging across multiple packages. This Skill orchestrates automated release workflows to streamline packaging processes.

Core Features & Use Cases

  • Discover which packages have unreleased changes and propose appropriate release types (major/minor/patch).
  • Bump versions, generate release notes, commit changes, tag releases, and push updates, while keeping inter-package dependencies in sync.
  • Generate per-package changelogs and ensure cross-package compatibility by updating minimum version constraints when needed.

Quick Start

Initiate the release workflow to automatically detect changes, decide releases, bump versions, generate release notes, and push tagged updates.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and changelog generation for a monorepo?

Automate version bumping and changelog generation by running a release workflow that discovers unreleased changes, proposes version increments, generates per-package release notes, and commits the updates for your monorepo.

How do I keep inter-package dependencies in sync when releasing multiple packages?

Keep inter-package dependencies in sync during release by automatically updating minimum version constraints across affected packages, ensuring cross-package compatibility when version bumps are applied to dependent code.

What is the best way to coordinate Git tagging and release notes across multiple packages?

Coordinate Git tagging and release notes by orchestrating scripted phases that decide per-package releases, bump versions, generate changelogs, commit changes, tag releases, and push updates end-to-end.

Can I automatically discover which packages in a monorepo have unreleased changes?

Discover unreleased changes automatically by initiating the workflow, which scans packages, identifies pending modifications, and proposes appropriate release types such as major, minor, or patch for each.

Does the release workflow enforce validation guardrails before pushing Git tags?

The release workflow enforces validation guardrails throughout its scripted phases, ensuring operational requirements are met and release decisions are validated before versions are bumped and tagged updates are pushed.