skills.rest
andymai
andymaiCOMMUNITY
Explore all skills by this author →
GitHub

release-publishing

Manage release-please and npm publishing workflows for the brepjs monorepo.

77|7|Updated Feb 1, 2026
Search Tags:#npm#monorepo#ci-cd#oidc#release-please#release-publishing#brepjs
One-click install
npx skills add https://github.com/andymai/brepjs --skill release-publishing-andymai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-publishing
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/release-publishing
Command: npx skills add https://github.com/andymai/brepjs --skill release-publishing-andymai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of outages, broken deployments, and failed publishes when managing releases for the brepjs JavaScript CAD monorepo, which has complex multi-package release sequencing, OIDC authentication requirements, and strict guardrails to avoid breaking changes to the public API.

Core Features & Use Cases

  • End-to-end release workflow guidance: Walks through the full release-please flow for the brepjs monorepo, including root and leaf package release ordering, auto-merge rules, and npm publishing steps.
  • Hard rule enforcement: Outlines non-negotiable guardrails to prevent common failures like ETARGET errors from mismatched package versions, broken npm auth from renamed workflow files, and accidental breaking changes to the public API.
  • Failure recovery playbooks: Provides step-by-step fixes for failed root/leaf publishes, conflicted release PRs, ETARGET CI errors, and pack validation failures.
  • Use Case: If a root brepjs npm publish fails after a release tag is created, this Skill provides the exact republish workflow command to fix the issue without creating duplicate tags or breaking the release sequence.

Quick Start

Use the release-publishing skill to recover a failed brepjs root npm publish by re-dispatching the release-please workflow in republish mode.

Frequently Asked Questions about release-publishing

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

FAQPage Schema
How do I fix a failed npm publish in a release-please monorepo after a tag is created?▼

To fix a failed npm publish, re-dispatch the release-please workflow in republish mode to retry the deployment without creating duplicate tags or breaking the release sequence.

Why does release-please show an ETARGET CI error during npm publishing?▼

An ETARGET error during npm publishing happens when package versions mismatch in the release-please configuration, requiring version alignment to resolve the CI failure.

How does OIDC trusted publisher authentication work for npm packages?▼

OIDC trusted publisher authentication secures npm publishing by using trusted identity tokens instead of static secrets, preventing broken auth from renamed workflow files.

What is the correct release sequence for root and leaf packages in a monorepo?▼

The correct release sequence for a monorepo requires ordering root package releases before leaf packages, enforcing strict merge rules to prevent deployment failures.

How do I resolve pack validation errors and conflicted release PRs?▼

Resolve pack validation errors and conflicted release PRs by following step-by-step recovery procedures that enforce guardrails for breaking change handling and merge order.

Can I use release-please to prevent breaking changes to a public API?▼

Release-please enforces non-negotiable guardrails to prevent accidental breaking changes to the public API, ensuring safe end-to-end release and npm publishing workflows.

Related Skills

Explore More Software Engineering Skills→
pr-pmpr-pm
121

npm-trusted-publishing

Configure GitHub Actions OIDC trusted publishing for npm packages.

Community
Intermediate
andymaiandymai
77

companion-packages

Resolve brepjs monorepo package structure, build order, and release pipeline issues.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced
dwmkerrdwmkerr
23

release-please-development

Automates version bumps, changelog generation, and GitHub releases via Release Please.

Community
Intermediate