Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »


    This package has been deprecated

    Author message:

    use 'cutarelease' package, hyphens were a mistake

    Use "python ./ ..." to make cutting a release of your project a single step. Basically, it will help cut a release for a git-based project that follows a few conventions. It'll update your changelog (, add a git tag, push those changes, update your version to the next patch level release and create a new changelog section for that new version. Also, it will optionally "npm publish" (for node projects with a package.json) and upload to pypi (for Python projects with a

    First, this script isn't useful unless you follow these conventions for your projects:

    project conventions

    I use git for version control.

    I use 'X.Y.Z' (aka major.minor.patch) versioning for all my projects. Increment the patch number for a bug fix. Increment the minor version for a change that adds functionality but doesn't break backward compatibility (or if you know for damn certain that your compat-change isn't going to break anyone). Increment the major version for major architectural changes and/or backward compatibility breakages.

    I write a change log file for my projects (example: json changelog). This is a manually edited file with a section for released and in-progress "interesting to the user" changes to the project. Yes, there is the commit history but that is often obtuse to the end user and hard to correlate to released versions. Basically you want to answer this user question: "I have version N, what will it mean for me to upgrade to version M."

    I tag my repo for each release using the version number as the tag name.

    The commited version number at the HEAD of the repo is for the next unreleased version. So, for example, if "1.2.3" is the latest released version, then the version at the repo HEAD is "1.2.4".

    state of this project

    I've just quickly put this into its own github repo. Likely this has some hiccups for general usage (i.e. is tailored to my specific usage). I will try to fix that and update here when I do that.

    I'm a Python and Node.js guy, so this script will probably need some love to be nice for Ruby, Perl, etc. folks.


    I tend to add a "make cutarelease" target. For example, in my json project I have something like this:

        python support/ -f package.json -f lib/jsontool.js

    A typical patch fix goes like this (example: json issue #23):


    Pick one of the following options:

    1. "" has no external deps (other than a fairly recent Python 2.x). You can just copy it over to your repo's tools directory.

    2. Git submodules. So something like:

      mkdir -p deps
      git submodule add deps/cutarelease
      git submodule update --init deps/cutarelease

      then use "deps/cutarelease/" in your Makefile.

    Eventually I may publish this to npm so you could npm install cutarelease, but I haven't done that yet.


    MIT. See LICENSE.txt.




    npm i cut-a-release

    Downloadsweekly downloads








    last publish


    • avatar