another-npm

A major breaking change 1.0.0 - (increases the major and pushes a release/publish)

Stats

stars 🌟issues ⚠️updated 🛠created 🐣size 🏋️‍♀️
00Mar 19, 2018Mar 9, 2018Minified + gzip package size for another-npm in KB

Readme

another-npm

A major breaking change 1.0.0 - (increases the major and pushes a release/publish)

A feature change 1.1.0 with breaking change - (increases the minor and pushes a release/publish)

A doc change 1.1.0 - no change

A feature change 1.2.0 without breaking change - (increases the minor and pushes a release/publish)

A Fix 1.2.1 - (increases the patch and pushes a release/publish)

A Style commit - no change

A Refactor - no change

A Perf - 1.2.2 - (increases the patch and pushes a release/publish)

A test - no change

A build - no change

A ci - no change

A chore - no change

A revert - no change

So.... 1.2.3 (Major.Minor.Patch)

  • Any type of commit can force a release/publish by answering yes to "Are there any breaking changes?"

  • Changes that trigger a release/publish (without having to answer yes to the breaking changes question)

    Type w/out breaking change with breaking change
    Feat increases minor increases major
    Fix increases patch increases major
    Perf increases patch increases major
  • Changes that do not trigger a release/publish (unless you answer yes to the breaking change question)

    • Doc
    • Style
    • Refactor
    • Test
    • Build
    • CI
    • Chore
    • Revert

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.