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

@livingdocs/release-tools

v3.6.2

Published

CLI tools for handling a release on git/github

Downloads

20

Readme

Release Tools

Greenkeeper badge

The release tools are a bunch of command line tools to maintain a release. These tools are usually used by a release manager.

Usage

Preconditions

Have npx installed with npm install -g npx

List of available commands

npx release-tools

Create Release Branch

Introduction When you want to manage a product with different releases and support old version with patches, you can not just use semver on master. You also have to work with release branches to support old versions. A more detailed explanation with an example can be found here

Commands

  • Help: npx @livingdocs/release-tools@<version> create-release-branch
  • Command (simple example): npx @livingdocs/release-tools@<version> create-release-branch --base-tag=v1.0.1 --release-branch-name=release-2017-10 --npm-token=<token>

Examples

Run the tests

npm test

Test the release tools locally

Change the directory to a repository you want to test the release tools with (e.g. livingdocs-server), the release tools will be executed in the context of the repository you are in. Both repositories should be in the same parent directory. Then run the following command:

node ../release-tools/bin/cmd.js create-release-branch \
  --repo=repoName \
  --base-tag=validVersion \
  --release-branch-name=test-release \
  --npm-token=validNPMToken

A validVersion is a tag that exists in the repository you are in and fulfils semver constraints:

  • latest version of minor bump (e.g. 1.2.latest)
  • newer minor or major version exist (e.g. 1.3.0 or 2.0.0 exist)

Copyright

Copyright (c) 2018 Livingdocs AG, all rights reserved

It is not permitted to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of this Software ('release-tools'), except when explicitly stated otherwise by Livingdocs AG.