release

Automate npm publishing and changelog generation by processing git-based commit history to group changes, bump semantic versions, and push the package to npm. This executes the full end-to-end release workflow in a single consistent process.

Semantic version bumping analyzes conventional commit message types like feat, fix, and chore to automatically determine if the next release should be a major, minor, or patch version update. It then applies this version bump directly to your package.json.

Yes, you can create a GitHub release and git tag simultaneously with npm publishing. The workflow handles version updates, atomic git commits, tagging, GitHub release creation, and npm distribution together to ensure a consistent, atomic release process.

Generate structured release notes by grouping recent git commits by their type, such as feat, fix, or chore. This creates clear, structured changelog entries for every version and eliminates the tedious manual effort of writing release notes.

Yes, the release workflow supports manually specifying a version number instead of relying on automatic semantic version bumping. You can provide a user-specified version number to override the automatic detection from commit message conventions.

Use an automated end-to-end release pipeline when you need consistent, atomic release processes with proper versioning and multi-platform distribution. It is ideal for git-based Node.js projects where manual versioning, git tagging, and npm publishing introduce repetitive effort and human error.