crowi-release

Orchestrates Crowi releases through pre-flight checks, Go/No-Go decisions, and post-tag artifact verification.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-release
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-release
Command: npx skills add https://github.com/crowi/crowi --skill crowi-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Crowi involves human judgment that CI cannot automate: deciding when to cut a release and confirming that npm packages, Docker images, and GitHub Releases actually shipped. This Skill standardizes those two human-side tasks so nothing is merged, tagged, or published without explicit approval and evidence.

Core Features & Use Cases

  • Pre-flight Go/No-Go report: Collects pending changesets, the open Version PR, main-branch CI status, commits since the last tag, unmerged worktrees, and a production-build smoke test into a single decision summary.
  • Post-release verification: Read-only checks that the Release and Docker workflows succeeded, every public workspace package was published to npm, Docker images pull and run, and the GitHub Release notes exist.
  • Manual fallback runbook: Step-by-step recovery path for publishing by hand when CI is broken, including Trusted Publisher and multi-arch buildx pitfalls.
  • Use Case: Before merging the changesets Version PR, run the pre-flight mode to see exactly what ships, what is excluded, and whether main is green; after the tag, run verify mode to confirm all artifacts landed.

Quick Start

Ask the agent to run the crowi-release pre-flight check and present the Go/No-Go decision materials for the next release.

Frequently Asked Questions about crowi-release

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

FAQPage Schema
How do I prepare a Go/No-Go decision for a changesets release?

Run the pre-flight mode, which collects pending changesets, the open Version PR, main-branch CI status, commits since the last tag, unmerged worktrees, and a production-build smoke test. It presents these as a decision summary and stops before any merge.

How do I verify npm packages and Docker images after a release tag?

Use verify mode with the release tag. It checks that Release and Docker workflows succeeded, confirms every public workspace package version on npm, pulls and smoke-runs the Docker images, and confirms the GitHub Release notes exist.

Does this release process merge or publish automatically?

No. Merging the Version PR, tagging, and publishing only happen after explicit user approval. Pre-flight and verify modes are read-only, and failed artifacts are reported with suggested actions rather than republished automatically.

What do I do when release CI is broken and I must publish manually?

Follow the manual fallback section: run changeset version, merge a release PR to main, tag the merged commit with the computed dist version, run changeset publish, and build multi-arch Docker images. Note that npm Trusted Publishing only works in CI, so manual publish needs a token or 2FA.

Why does the Docker image build not trigger after pushing the release tag?

Tag pushes use GITHUB_TOKEN, whose anti-recursion protection does not trigger the Docker workflow directly. The Docker build chains off the Release workflow via workflow_run, so images build only when an actual publish occurred.