release-npm-trustme

Automate npm package releases by bumping semver versions, building artifacts, tagging commits, and publishing. This end-to-end workflow requires a clean working tree, pnpm, tsx, and optionally the gh CLI for GitHub Release creation.

An end-to-end npm release workflow handles version bumping, project building, commit tagging, and publishing. You need this automation when manual release toil increases error risk across versioning and deployment steps.

You do not need the GitHub CLI to publish npm releases, but it is required optionally to create or update a GitHub Release. When gh is available, it uses CHANGELOG.md notes to describe release changes.

Run a specific semver version bump by invoking pnpm tsx scripts/release.ts with your desired version increment. You can choose patch, minor, major, or an exact version string to build and publish.

If your git working tree is not clean before a release, the automation guardrails halt the process. A clean working tree is required to ensure version bumps and commit tagging proceed without uncommitted conflicts.

Yes, you can use CHANGELOG.md notes for automated GitHub Release descriptions. When the gh CLI is available, the release workflow automatically extracts and applies these notes to describe published changes.