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 🙏

© 2024 – Pkg Stats / Ryan Hefner

release-automation

v0.7.0

Published

An opinionated CLI for release automation

Downloads

16

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

evansowinoevansowino

Keywords

githubreleaserelease-automationsemver

Readme

release-automation

npm version

What

An opinionated CLI for release automation

Prerequisites

This CLI requires Node 9.11.2 or higher.

Installation

BEFORE YOU INSTALL: please read the prerequisites

npm install -g release-automation

Usage

Then simply run the following in your git instantiated directory

release-automation

Use any of the following flags to print the version of the module: -v, --v, -version, --version

Steps

  1. Prompts you for a branch name. If you don't provide one, the current branch will be used. If you do provide a branch name, you will be asked which branch to base it on. The master branch will be used as default. Given both are provided, a new branch will be created.

  2. Select the branches you want to merge into the selected branch from step 1. Also optional, as you may have done this already.

  3. It will attempt to merge the selected branches into the current branch. All successful merges will be printed displayed. If any merge conflicts are raised, the process will exit and give you the chance to resolve them. Once resolved, you can run the script again.

  4. Prompts you for the next version of your release. It will suggest one by looking at your current version in package.json and the branches you have selected. For example, if you're currently on version 1.0.0, and you have selected 2 branches where the names begin with feat/ and 1 branch that begins with fix/, then the suggested version will be 1.2.1. The suggested version will be used as the default version for the next release if you don't provide one. Other semver versions are not suggested for simplicity, but you may specify.

  5. It will then set npm version which will subsequently also git tag the release. If that fails (e.g. package.json doesn't exist), it will set the git tag version manually.

  6. The current branch will then be pushed with tags to github.

  7. Prompts you if you'd like to create a PR into a staging branch, if you would, provide the staging branch

  8. A Github link will be printed that directs you to the PR page for the branch you specified into the staging branch

  9. A Github link to the release notes page for that release will also be printed.