finds.dev

mikeal/merge-release

Automatically release all merges to master on npm.

View on GitHub

★ 480JavaScriptNOASSERTIONupdated Jun 2023

// the take

A GitHub Action that auto-publishes to npm on every merge to master, inferring semver bump from commit messages (BREAKING CHANGE → major, feat → minor, everything else → patch). Zero config beyond two secrets. Aimed at maintainers who want hands-off releases without setting up a full release toolchain.

The commit message parsing covers the common conventional-commits subset without requiring a strict format — 'feat:' and 'feature:' both work. It queries npm for the latest published version rather than trusting the local package.json, which prevents version drift if someone forgets to bump manually. The DEPLOY_DIR/SRC_PACKAGE_DIR split is useful for monorepos where you build into a dist folder before publishing.

Pinning usage to @master is actively dangerous — any push to the author's master silently changes your CI behavior with no version lock. There's no dry-run mode, so you can't test what version would be bumped before committing the workflow. The version inference is a blunt instrument: a commit that says 'feat: fix typo in docs' bumps minor, which is wrong. Last meaningful commit was 2023 and the issue tracker has open reports of it breaking on newer GitHub Actions runners, so there's a non-trivial chance it fails on a fresh setup today.

We read the README, the directory tree and a key source file in July 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
480
Forks
61
Language
JavaScript
License
NOASSERTION
Last commit
12 Jun 2023

// nearby

If merge-release isn't quite it.

All repos →