release

Bump versions, generate changelogs, and trigger GitHub Actions for the screenpipe monorepo.

20.9k|2.1k|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/screenpipe/screenpipe --skill release-screenpipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/screenpipe/screenpipe/tree/main/.claude/skills/release
Command: npx skills add https://github.com/screenpipe/screenpipe --skill release-screenpipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release of the Screenpipe monorepo is a multi-package operation that currently requires manual coordination across components. This Skill automates version bumps, changelog generation, and triggering of GitHub Actions pipelines to ensure consistent, error-free publishing.

Core Features & Use Cases

  • Bump versions across all monorepo components in a coordinated manner.
  • Generate a consolidated changelog from commits since the last release.
  • Trigger and monitor CI workflows for the app, CLI, MCP, and JavaScript packages.
  • Prepare release artifacts and ensure publishing workflows run to completion.

Quick Start

Follow the Release Workflow described in the Skill documentation:

  1. Check current versions across all components.
  2. Generate changelog for changes since the last release.
  3. Bump per-component versions and commit changes.
  4. Push changes and trigger the draft release workflow.
  5. Monitor builds and publish when ready.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate monorepo release versioning across multiple packages?

Automate monorepo release versioning by coordinating per-component version bumps in their manifest files, building a consolidated changelog from commits, and triggering GitHub Actions pipelines for each package.

How are changelogs generated from commits during a monorepo release?

Changelogs are generated by collecting and consolidating commit history since the last release across all monorepo components, producing a unified log of changes before triggering CI workflows.

Can I trigger GitHub Actions publishing pipelines for different monorepo components separately?

Yes, the release process enforces per-component version bumps and triggers the corresponding GitHub Actions publishing workflows for the app, CLI, MCP, and JavaScript packages individually.

What is the best way to coordinate cross-repo updates in a monorepo release?

Coordinate cross-repo updates by bumping component versions in their manifests, generating a consolidated changelog, committing changes, and pushing to trigger draft release workflows across the monorepo.

Does automated monorepo versioning require manual checks of current component versions?

The automated release workflow begins by checking current versions across all components, then generates changelogs, bumps versions, commits, and pushes changes to trigger CI.

What happens if a CI workflow fails during a multi-package monorepo release?

The release workflow monitors builds after triggering draft release workflows, ensuring publishing workflows run to completion before finalizing the release artifacts across all components.