{"action":"created","issue":{"url":"https://api.github.com/repos/semantic-release/semantic-release/issues/835","repository_url":"https://api.github.com/repos/semantic-release/semantic-release","labels_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/835/labels{/name}","comments_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/835/comments","events_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/835/events","html_url":"https://github.com/semantic-release/semantic-release/issues/835","id":336432981,"node_id":"MDU6SXNzdWUzMzY0MzI5ODE=","number":835,"title":"Add way to pass in build meta data (or modify the version in general)","user":{"login":"jamsea","id":614910,"node_id":"MDQ6VXNlcjYxNDkxMA==","avatar_url":"https://avatars3.githubusercontent.com/u/614910?v=4","gravatar_id":"","url":"https://api.github.com/users/jamsea","html_url":"https://github.com/jamsea","followers_url":"https://api.github.com/users/jamsea/followers","following_url":"https://api.github.com/users/jamsea/following{/other_user}","gists_url":"https://api.github.com/users/jamsea/gists{/gist_id}","starred_url":"https://api.github.com/users/jamsea/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamsea/subscriptions","organizations_url":"https://api.github.com/users/jamsea/orgs","repos_url":"https://api.github.com/users/jamsea/repos","events_url":"https://api.github.com/users/jamsea/events{/privacy}","received_events_url":"https://api.github.com/users/jamsea/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-06-28T00:29:52Z","updated_at":"2018-06-28T17:09:10Z","closed_at":null,"author_association":"NONE","body":"## New feature motivation\r\n\r\nI want to be able to add the Jenkins build number as metadata using this feature in semver: https://semver.org/#spec-item-10\r\n\r\nCurrently there's no way to modify/parse the version that I know of.\r\n\r\n## New feature description\r\n\r\nI think what could make the most sense is the ability to pass in a `parseVersion` function into `release.config.js`. This function would take in a version number and return a string.\r\n\r\n## New feature implementation\r\n\r\nIt looks like this file is currently figuring out the version:\r\nhttps://github.com/semantic-release/semantic-release/blob/caribou/lib/get-next-version.js\r\n\r\nOne potential solution is to pass in a `parseVersion` function that returns a new version and change line 7 to\r\n```js\r\nversion = parseVersion(semver.inc(lastRelease.version, type));\r\n```\r\n\r\n<!-- Optionally describe the technical changes to be made in semantic-release or its plugins. -->\r\n"},"comment":{"url":"https://api.github.com/repos/semantic-release/semantic-release/issues/comments/401106918","html_url":"https://github.com/semantic-release/semantic-release/issues/835#issuecomment-401106918","issue_url":"https://api.github.com/repos/semantic-release/semantic-release/issues/835","id":401106918,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMTEwNjkxOA==","user":{"login":"jamsea","id":614910,"node_id":"MDQ6VXNlcjYxNDkxMA==","avatar_url":"https://avatars3.githubusercontent.com/u/614910?v=4","gravatar_id":"","url":"https://api.github.com/users/jamsea","html_url":"https://github.com/jamsea","followers_url":"https://api.github.com/users/jamsea/followers","following_url":"https://api.github.com/users/jamsea/following{/other_user}","gists_url":"https://api.github.com/users/jamsea/gists{/gist_id}","starred_url":"https://api.github.com/users/jamsea/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamsea/subscriptions","organizations_url":"https://api.github.com/users/jamsea/orgs","repos_url":"https://api.github.com/users/jamsea/repos","events_url":"https://api.github.com/users/jamsea/events{/privacy}","received_events_url":"https://api.github.com/users/jamsea/received_events","type":"User","site_admin":false},"created_at":"2018-06-28T17:09:10Z","updated_at":"2018-06-28T17:09:10Z","author_association":"NONE","body":"I see what you mean. I think I've been thinking about this wrong, this might be the wrong tool for the job I have (even though it'd be great to use for a new, or smaller project). Now that I'm thinking more about it, it's going to be tricky to get the git history too, because I'll be running this from inside a docker container that won't have the entire repo (just a sub folder), so I won't have access to the `.git` folder to read the tags. Do you know if the npm plugin determines the next version by checking the npm server? Or does it rely on git tags and the package.json?\r\n\r\n"}}
{"actor":{"display_login":"jamsea"}}