npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

release-suite

v3.2.1

Published

Semantic versioning and release automation toolkit for Git-based projects.

Readme

🎉 Release Suite

Semantic versioning and release automation toolkit for Git-based projects.

Designed for safe, predictable, and fully automated releases across multiple Git providers.


🚀 Features

Core

  • Automatic version bump based on commit messages
  • Conventional commit parsing (customizable)
  • Deterministic changelog generation
  • Create an annotated Git tag for a release
  • Release notes generation with provider APIs
  • Dry-run mode for safe previews

🌍 Multi-Provider Support

| Provider | Changelog | Release Notes | | --------- | --------- | ------------- | | GitHub | ✅ | ✅ API | | GitLab | ✅ | ✅ API | | Bitbucket | ✅ | ⚠ Fallback |

🔗 Smart Changelog

  • PR + Issue detection (#123)
  • Multiple references per commit
  • Automatic link generation
  • Provider-aware URLs

Example:

- feat: add login ([#34](...), [#12](...))

🧠 Release Notes Engine

  • Uses provider APIs when available
  • Automatic fallback to local generation
  • Zero configuration required

⚙️ Architecture

Core Engine
   ↓
Provider Adapter (GitHub / GitLab / Bitbucket)
   ↓
API (optional)
   ↓
Fallback (always available)

See docs/architecture.md for a detailed design overview of the core engine, provider adapters, and fallback strategy.


⚡ Quick Start

npm install release-suite --save-dev

Add to your project's package.json:

{
  "scripts": {
    "dry-run": "rs-dry-run create",
    "dry-run:clean": "rs-dry-run remove",
    "version:compute": "rs-version compute",
    "changelog": "rs-changelog generate",
    "release-notes": "rs-release-notes generate",
    "tag:create": "rs-tag create"
  }
}

Generate dry-run files without touching your real changelog:

npm run dry-run

Remove dry-run files:

npm run dry-run:clean

⚙️ Configuration

Release Suite can be configured using a release.config.js file.

This file controls:

  • Git tag prefix (v1.2.3 vs 1.2.3)
  • Emoji usage in changelog rendering
  • Commit-to-version mapping (via releaseRules)

See docs/config.md for full documentation.


🖥️ CLI Commands

| Command | Description | | --------------------------- | ---------------------------------------------------------- | | rs-version compute | Computes next semantic version based on git commits | | rs-changelog generate | Generates a new changelog entry for the next release | | rs-changelog rebuild ⚠️ | Fully rebuilds CHANGELOG.md from git history (Danger Zone) | | rs-release-notes generate | Generates RELEASE_NOTES.md | | rs-dry-run create | Generates dry-run changelog & release notes | | rs-dry-run remove | Removes dry-run changelog & release notes | | rs-tag create | Creates and pushes a git tag |

Each command follows a strict and predictable CLI contract (exit codes, stdout, JSON mode).

💡 Note about execution

⚠️ rs-changelog rebuild is a destructive operation. Always use --dry-run first.

  • When using these commands via npm run, they can be referenced directly (rs-*).
  • In CI/CD environments (e.g. GitHub Actions), always invoke them using npx (e.g. npx rs-changelog generate) to ensure proper binary resolution.

🔁 Release Flow

This project uses an automated, PR-based release strategy designed for safety and traceability.

See Release Process for details.


🤖 CI/CD

ℹ️ In CI/CD environments, always use npx when invoking rs-* commands.

This project is designed to be used in automated pipelines.

👉 See full examples in docs/ci.md.


🧩 Programmatic API

Release Suite also exposes a programmatic API for advanced use cases (integration tests, custom tooling, orchestration).

👉 See full API documentation in docs/api.md


🛠 Development (Maintainers)

When working inside the release-suite repository itself, the CLI binaries are not available via npm or npx, since they are not installed as a dependency.

In this case, run the scripts directly with Node.js:

node bin/version.js compute
node bin/changelog.js generate
node bin/release-notes.js generate
node bin/dry-run.js create
node bin/tag.js create

To test the CLI as a real consumer, you can use:

npm link
# or
npm install ../release-suite

📄 License

This project is licensed under the MIT License.


✨ Author

💼 LinkedIn 💻 GitHub