{"action":"created","issue":{"url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/62","repository_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver","labels_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/62/labels{/name}","comments_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/62/comments","events_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/62/events","html_url":"https://github.com/neo4j/neo4j-javascript-driver/issues/62","id":148792337,"number":62,"title":"Inconsistent prerelease version number casing confuses npm","user":{"login":"cybersam","id":196421,"avatar_url":"https://avatars.githubusercontent.com/u/196421?v=3","gravatar_id":"","url":"https://api.github.com/users/cybersam","html_url":"https://github.com/cybersam","followers_url":"https://api.github.com/users/cybersam/followers","following_url":"https://api.github.com/users/cybersam/following{/other_user}","gists_url":"https://api.github.com/users/cybersam/gists{/gist_id}","starred_url":"https://api.github.com/users/cybersam/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cybersam/subscriptions","organizations_url":"https://api.github.com/users/cybersam/orgs","repos_url":"https://api.github.com/users/cybersam/repos","events_url":"https://api.github.com/users/cybersam/events{/privacy}","received_events_url":"https://api.github.com/users/cybersam/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-15T23:34:40Z","updated_at":"2016-04-18T08:47:18Z","closed_at":null,"body":"I noticed that some prerelease version numbers are lowercased (e.g., “-alpha.1”), and some are uppercased (e.g., “-M01” and “-RC1”).\r\n\r\nThis causes problems/confusion for node.js clients because `npm`, the node.js package manager, orders prerelease versions alphabetically (with uppercase letters coming before lowercase letters).\r\n\r\nSo, npm believes the `alpha` versions are more recent than the `M` and `RC` versions.\r\n\r\nCan neo4j's node.js packages start using lowercasing for all prerelease version numbers, to avoid this in the future? If the possible prerelease version prefixes are, say (in order of freshness): \"alpha\", \"beta\", \"m\", and \"rc\", this would be a way to solve this issue.\r\n\r\nFor example, if the next RC version were to be \"1.0.0-rc3\", then npm would properly consider it (and not \"1.0.0-alpha7\") to be the highest prerelease version for 1.0.0."},"comment":{"url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/comments/211275510","html_url":"https://github.com/neo4j/neo4j-javascript-driver/issues/62#issuecomment-211275510","issue_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/62","id":211275510,"user":{"login":"pontusmelke","id":88000,"avatar_url":"https://avatars.githubusercontent.com/u/88000?v=3","gravatar_id":"","url":"https://api.github.com/users/pontusmelke","html_url":"https://github.com/pontusmelke","followers_url":"https://api.github.com/users/pontusmelke/followers","following_url":"https://api.github.com/users/pontusmelke/following{/other_user}","gists_url":"https://api.github.com/users/pontusmelke/gists{/gist_id}","starred_url":"https://api.github.com/users/pontusmelke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pontusmelke/subscriptions","organizations_url":"https://api.github.com/users/pontusmelke/orgs","repos_url":"https://api.github.com/users/pontusmelke/repos","events_url":"https://api.github.com/users/pontusmelke/events{/privacy}","received_events_url":"https://api.github.com/users/pontusmelke/received_events","type":"User","site_admin":false},"created_at":"2016-04-18T08:47:18Z","updated_at":"2016-04-18T08:47:18Z","body":"Thanks for pointing this out, we'll make sure to be more consistent about casing in upcoming releases... "}}