ianstormtaylor / bump Goto Github PK

When scripting releases, it becomes a pain to use bump because it outputs human-friendly text all the time. It would be nice if there was a machine-friendly way to use it:

$ bump minor --print-version
1.2.0

$ bump patch --print-manifests
package.json
component.json

I'm not sure what the best API would be for this, but currently needing to use egrep to extract the new version number is awkward.

if package.json is private then ignore it if it doesnt have a version key, so that you can have private pieces next to public components or vice versa

Is it possible to submit this to npm? I know there is already a bump out there and that would require a different package name, but npm doesn't appear to know, once it's installed, that it came from github. When checking for updates, it reverts to installing the package named bump from npm. I can update it with the namespace manually, but if I ever need to do a general npm -g update, it gets overwritten.

should probably be more graceful, so you don't need to think about... "okay, this component has a package.json"

/usr/local/lib/node_modules/bump/bin/bump:45
  version = increment(files['package.json'].version, version);

Bump do not update lock-file (npm-shrinkwrap.json), I think it should.