release_skill

This skill automates releasing all screenpipe monorepo components, bumps versions, generates changelogs, and triggers CI workflows to streamline shipping.

Rust

16.9k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill screenpipe/screenpipe --skill release

SKILL.md6.1 KB

Overview

This skill automates releasing the screenpipe monorepo. It bumps package versions, generates a customer-facing changelog, and triggers GitHub Actions workflows for the desktop app, CLI/server, MCP, and JavaScript packages. It keeps releases consistent across Rust and JS components while creating draft releases for manual verification.

How this skill works

It inspects version files across the repo (Cargo.toml for app and CLI, package.json for MCP and JS packages), updates the appropriate version entries, and commits the changes. It can run a changelog generator (Anthropic-backed script) or help produce a manual JSON changelog, then triggers the repo workflows via gh to create draft releases. The skill also provides commands to monitor CI runs, test draft artifacts, and publish when ready.

When to use it

After meaningful changes to core libraries or services (screenpipe-core, vision, audio, server, db, events, integrations) — always release the CLI when these change
For UI/frontend-only changes under screenpipe-app-tauri, perform an app-only release
When you need a coordinated multi-package release across Rust and JS packages
When you want a draft release to test updater artifacts and installer bundles before publishing

Best practices

Only include changes that deliver clear customer value in the changelog; skip CI, refactors, dependency bumps, and merge commits
Generate the changelog via the automated script when ANTROPIC_API_KEY is available to preserve consistent summaries
Always pull --rebase before pushing to avoid merge conflicts on version commits
Run GH workflows as draft first and verify updater artifacts (.tar.gz/.nsis.zip and .sig) on macOS and Windows before publishing
Use the provided git commands to find the last CLI release and diff core directories to decide if a CLI bump is required

Example use cases

App-only UI tweak: bump the app Cargo.toml, run the app workflow, test draft builds on macOS and Windows, then publish
Core change affecting runtime: bump CLI workspace version, regenerate changelog, trigger release-cli workflow and related package workflows
Publishing JS SDKs: update package.json for browser and node SDKs and run npm publish after the CI jobs succeed
Emergency fix: create a focused changelog entry, bump the affected package, trigger its workflow, rerun failed jobs if needed

FAQ

No. workflow_dispatch creates a draft only. You must publish manually or push a commit with the magic message to auto-publish.

How do I check what changed since the last CLI release?

Locate the last CLI release commit via git log for the CLI bump message, then run git diff <COMMIT>..HEAD --stat against core directories to see relevant changes.