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

rn-release-automator

v0.1.0

Published

CLI tool to automate the React Native release process

Readme

⚛️ rn-release-automator

A CLI tool that automates the React Native release process — branch cuts, cherry-picks, publishing, testing, and announcements.

Built for the React Native Release Crew. Guides you step-by-step through every phase of a release with interactive prompts, pre-flight checks, and GitHub API integrations.

Install

npx rn-release-automator

Or install globally:

npm install -g rn-release-automator

Usage

Run without arguments for the interactive menu:

rn-release-automator

Or invoke commands directly:

rn-release-automator status
rn-release-automator status --series 0.85
rn-release-automator prepare-release --series 0.85
rn-release-automator publish --version 0.85.0-rc.1

Use --dry-run to preview any command without making changes:

rn-release-automator --dry-run
rn-release-automator publish --version 0.85.0 --dry-run

Use --help on any command to see available flags:

rn-release-automator --help
rn-release-automator cut-branch --help

Commands

Commands follow the React Native release lifecycle. Each links to its corresponding guide in reactwg/react-native-releases.

| Command | Description | |---------|-------------| | init | Validate environment — tools, tokens, repo access, bot merger list | | status | Overview of all release series, or details for a specific one | | cut-branch | Full branch cut workflow — CI check, create branch, template, Discord, Hermes | | create-github-project | Clone and configure a GitHub Project for tracking a release | | prepare-release | Analyze pick requests, determine next version, process picks via bot | | publish | Pre-flight checks, trigger create-release.yml workflow, monitor | | test-release | Verify repo/branch, clean env, download prebuilds, test matrix | | verify-release | Interactive 8-step post-release verification (npm, template, Maven, etc.) | | post-promotion | Update support policy, ship blog post, cut new website version | | communicate | Generate announcement templates (Discord, GitHub, status tracker) |

Release Workflow

A typical release follows these steps:

1. init              → verify your environment is set up
2. cut-branch        → create the stable branch (RC0 only)
3. create-github-project → set up the release tracking project
4. prepare-release   → cherry-pick fixes, analyze pending picks
5. publish           → trigger the create-release workflow
6. test-release      → run through the test matrix
7. verify-release    → verify npm, Maven, template, changelog
8. post-promotion    → update website, blog, support policy
9. communicate       → generate and post announcements

For patch releases, skip steps 2-3 and start at prepare-release.

Prerequisites

  • Node.js >= 18
  • GitHub CLI (gh) authenticated — gh auth login
  • Git with push access to facebook/react-native
  • For project management: gh auth refresh -s project (adds the project scope)

The init command checks all of these for you.

Features

Smart Pick Analysis

prepare-release analyzes each pending pick request and classifies it:

  • 🟢 Bot merge — commit is on main, can use @react-native-bot merge
  • 🟡 Not on main — commit hasn't landed on main yet
  • 🔵 PR on branch — PR targets the stable branch directly
  • 🟢 Already merged — PR is merged but pick request is still open
  • 🔴 Hermes — involves facebook/hermes, needs a Hermes release
  • 🔴 Multi-target — targets multiple branches, needs duplication
  • 🔴 Complex — multiple PRs/commits, needs manual review

Support Tiers

status shows versions grouped by support tier:

  • Future — scheduled versions and active RCs
  • Active — latest 2 stable series
  • End of Cycle — 3rd latest stable series
  • Unsupported — everything older

Dry Run

--dry-run skips all mutations (workflow triggers, comments, branch creation, git push) but still runs read-only checks (CI status, npm queries, pick analysis). Every prompt shows a red DRY RUN badge.

Configuration

The CLI auto-discovers your GitHub token from:

  1. GITHUB_TOKEN environment variable
  2. gh auth token (GitHub CLI)

No configuration files needed.

Repositories

The CLI interacts with these repositories:

Development

git clone https://github.com/cortinico/rn-cli.git
cd rn-cli
npm install
npm run build    # strip Flow types → dist/
npm start        # run the CLI
npm run dev      # build + run in one step

The project uses Flow for type checking:

npm run flow

License

MIT