release-engine

Automating an npm package release with pre-flight audits requires a workflow that checks rules compliance, bumps versions, and creates tags before publishing. This engine automates that end-to-end process while refusing auto-execution for explicit consent.

The safest way to publish using gh-cli requires explicit user invocation rather than automatic execution. This engine enforces that safeguard, applying pre-flight audits and smoke-tests after publish to prevent uncontrolled releases.

Release-notes generation fails with a 404 on draft URLs because the underlying API cannot resolve unpublished draft resources. This engine specifically knows about and avoids the gh-cli release-notes trap and draft-URL 404 trap during automation.

Running a smoke-test after an npm publish requires sequencing the validation step immediately following the publication action. This engine orders the workflow to execute release-notes before publish and smoke-testing after publish.

Using this release automation engine for projects without CLAUDE.md rules is not optimal because it specifically cuts releases per CLAUDE.md guidelines. It expects explicit invocation and compliance with those defined rules.