{"action":"opened","issue":{"url":"https://api.github.com/repos/keystonejs/keystone/issues/924","labels_url":"https://api.github.com/repos/keystonejs/keystone/issues/924/labels{/name}","comments_url":"https://api.github.com/repos/keystonejs/keystone/issues/924/comments","events_url":"https://api.github.com/repos/keystonejs/keystone/issues/924/events","html_url":"https://github.com/keystonejs/keystone/issues/924","id":54726231,"number":924,"title":"Use semver semantic for npm.","user":{"login":"Calvein","id":243189,"avatar_url":"https://avatars.githubusercontent.com/u/243189?v=3","gravatar_id":"","url":"https://api.github.com/users/Calvein","html_url":"https://github.com/Calvein","followers_url":"https://api.github.com/users/Calvein/followers","following_url":"https://api.github.com/users/Calvein/following{/other_user}","gists_url":"https://api.github.com/users/Calvein/gists{/gist_id}","starred_url":"https://api.github.com/users/Calvein/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Calvein/subscriptions","organizations_url":"https://api.github.com/users/Calvein/orgs","repos_url":"https://api.github.com/users/Calvein/repos","events_url":"https://api.github.com/users/Calvein/events{/privacy}","received_events_url":"https://api.github.com/users/Calvein/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-19T04:54:27Z","updated_at":"2015-01-19T04:54:27Z","closed_at":null,"body":"The latest version (`0.2.41`) added a couple of functionalities that break (for us) what we had in `0.2.40`. If the versions were following [semver] we wouldn't had have problems since we use the ~, is there any reason why it's not the case ? Just FYI:\r\n\r\n> 1. MAJOR version when you make incompatible API changes,\r\n> 2. MINOR version when you add functionality in a backwards-compatible manner, and\r\n> 3. PATCH version when you make backwards-compatible bug fixes.\r\n\r\n[semver]: http://semver.org/"}}