{"action":"created","issue":{"url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/81","labels_url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/81/labels{/name}","comments_url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/81/comments","events_url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/81/events","html_url":"https://github.com/watson-developer-cloud/nodejs-wrapper/issues/81","id":104360481,"number":81,"title":"Use `npm version` for releases rather than manually changing the package.json version","user":{"login":"nfriedly","id":114976,"avatar_url":"https://avatars.githubusercontent.com/u/114976?v=3","gravatar_id":"","url":"https://api.github.com/users/nfriedly","html_url":"https://github.com/nfriedly","followers_url":"https://api.github.com/users/nfriedly/followers","following_url":"https://api.github.com/users/nfriedly/following{/other_user}","gists_url":"https://api.github.com/users/nfriedly/gists{/gist_id}","starred_url":"https://api.github.com/users/nfriedly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nfriedly/subscriptions","organizations_url":"https://api.github.com/users/nfriedly/orgs","repos_url":"https://api.github.com/users/nfriedly/repos","events_url":"https://api.github.com/users/nfriedly/events{/privacy}","received_events_url":"https://api.github.com/users/nfriedly/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-01T21:41:32Z","updated_at":"2015-09-04T21:21:48Z","closed_at":null,"body":"Standard practice with node.js modules is to commit all of the changes for a release *except updating the package.json version*, and then run the following:\r\n\r\n```sh\r\nnpm version major|minor|patch\r\ngit push --tags\r\nnpm publish\r\n```\r\n`npm version *` will update the package.json version field appropriately *and* create a git commit and tag for the version.  `git push --tags` will publish the tag to github, and then immediately running `npm publish` ensures no changes have a chance to sneak in.\r\n\r\nThe reason for this is that it allows someone to easily view the source code (and readme) for whatever version they happen to have downloaded from npm. This is particularly helpful when github is ahead of npm - right now there isn't any straightforward way to view what git commit matches the current npm release."},"comment":{"url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/comments/137856347","html_url":"https://github.com/watson-developer-cloud/nodejs-wrapper/issues/81#issuecomment-137856347","issue_url":"https://api.github.com/repos/watson-developer-cloud/nodejs-wrapper/issues/81","id":137856347,"user":{"login":"germanattanasio","id":313157,"avatar_url":"https://avatars.githubusercontent.com/u/313157?v=3","gravatar_id":"","url":"https://api.github.com/users/germanattanasio","html_url":"https://github.com/germanattanasio","followers_url":"https://api.github.com/users/germanattanasio/followers","following_url":"https://api.github.com/users/germanattanasio/following{/other_user}","gists_url":"https://api.github.com/users/germanattanasio/gists{/gist_id}","starred_url":"https://api.github.com/users/germanattanasio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/germanattanasio/subscriptions","organizations_url":"https://api.github.com/users/germanattanasio/orgs","repos_url":"https://api.github.com/users/germanattanasio/repos","events_url":"https://api.github.com/users/germanattanasio/events{/privacy}","received_events_url":"https://api.github.com/users/germanattanasio/received_events","type":"User","site_admin":false},"created_at":"2015-09-04T21:21:48Z","updated_at":"2015-09-04T21:21:48Z","body":":+1: "}}