googlearchive/appengine-nodejs

Versioning

Closed this issue · 4 comments

Guuz commented

Hello,

When will this module have active versioning? Right now I have to force a new download (using npm) to get the new features; because the version number did not change. Also for real world usage we would like to lock down the version when rolling out a release.

rrch commented

Now seems like a good time. I bumped the version to 0.0.2.

I'll look into pushing the library to npmjs.org.

stephenplusplus commented

Sorry to creep in here. I saw the issue in my feed and thought I might be able to help.

Quick Steps:

  1. npm login (this will create a user)
  2. npm version minor (this tags 0.1.0, and updates package.json)
  3. git push origin master --tags (pushes the changes & tag upstream)
  4. npm publish

More information:

A little-known command that handles tagging and updating package.json for you is simply:

$ npm version __incrementType__

Where incrementType is either: major, minor, or patch. These terms come from the http://semver.org spec, but to boil down the most important thing:

While less than 1.0, increase the minor if the API breaks.

After you hit 1.0, increase the major if the API breaks.

I would start with npm version minor, which will give you 0.1.0.

After you run the command, you just push up master with the --tags command to carry the tags, then $ npm publish.

Super more information:

https://www.npmjs.org/doc/misc/npm-developers.html

Guuz commented

Thanks, the both of you! :) I'll close this.

rrch commented

Thanks Stephen. I'll follow that workflow.