release

Publishes versioned npm releases of a React design system via a provenance-signed GitHub Actions workflow.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill release-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/release
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill release-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing an npm package is irreversible — a version number can never be reused, even after unpublishing — and this repo's release involves three version files that must agree, a dry-run consumer smoke test, OIDC trusted publishing, and tagging the exact published commit. This Skill walks through that entire procedure with the guardrails that prevent the known failure modes. ## Core Features & Use Cases - Version bump orchestration: Updates the authoritative PACKAGE_VERSION in scripts/package-manifest.mjs, the root package.json mirror, and the lockfile, then regenerates version-stamped derived files so CI's drift guard passes. - Dry-run validation: Runs the Release workflow in dry-run mode to build the tarball and install it into a scratch Vite + React app, proving a real consumer can build it before anything ships. - Provenance-signed publish and tagging: Publishes via npm publish --provenance with OIDC trusted publishing, verifies registry propagation without re-running on a 404, and tags the exact published commit with a GitHub Release. - Use Case: After merging a new component, ask to cut a minor release — the Skill checks what shipped since the last tag, bumps all three version locations, dry-runs the workflow, publishes, and tags the published commit. ## Quick Start Ask the assistant to cut a release of the design system, for example by saying "cut a patch release of @robr0/design-system and publish it to npm".

Frequently Asked Questions about release

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

FAQPage Schema
How do I publish a new version of an npm package with GitHub Actions?

Bump the version in the manifest, package.json, and lockfile, commit and push, then dispatch the Release workflow with dry_run=false. The workflow builds dist/, runs npm publish --access public --provenance, and signs a provenance attestation tied to the commit.

How do I decide between a patch, minor, or major version bump?

Use patch for bug fixes and docs, minor for additive changes like new components, exports, or tokens, and major for renamed or removed props, exports, or tokens. Review git log since the last tag to justify the choice before bumping.

Why does npm view return 404 right after a successful publish?

The npm registry lags a successful publish by several minutes, so a 404 immediately after a green workflow is propagation delay, not failure. Confirm the publish step logged the version line and never re-run the workflow, since the version is already consumed and a rerun fails with EPUBLISHCONFLICT.

Why does npm publish fail with a 404 on PUT during the workflow?

A 404 on PUT during publish is an authentication failure, not a missing package — npm returns 404 instead of 403 to avoid leaking package existence. Check the OIDC trusted publishing setup: no registry-url in actions/setup-node, id-token: write permission present, and the workflow file still named release.yml.

Can I publish the package from my local machine with npm publish?

No, local publishes are prohibited in this repo. All releases go through the Release workflow so every version is provenance-signed and smoke-tested in a scratch consumer app before shipping.