IssueRaiser

Add an option to output the version that would be published

# Feature request ## New feature motivation I am currently implementing automatic releases for my project, which is a web application. The project currently satisfies my needs as I can disable the npm plugins and replace it with gitlab plugins. The problem is that I need to put the version of my project into the built application (via Webpack's DefinePlugin), but the version field of my package.json is always set to 0.0.0. I would like to be able to use semantic-release to print the version that would be published and use it in webpack DefinePlugin. Currently, the only way to do that would be to parse the output of a dry-run, but it is complicated and not stable. ## New feature description I see two ways this could happen : * The simple one is to provide a cli option to instruct semantic release to just print the version. For example `semantic-release --print-next-version` * Allow a more extensive programmatic usage of semantic-release, with a JS api that would (among other things) allow to retrieve the next version. I could open a PR for the first solution if you'd like. The second one is a bigger task (probably several tasks)

Posted by BenoitAverty on Apr 24, 2018, 3:52 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

github (Other)

Add an option to output the version that would be published

BenoitAvertyApr 24, 2018, 3:52 PM

# Feature request ## New feature motivation I am currently implementing automatic releases for my project, which is a web application. The project currently satisfies my needs as I can disable the npm plugins and replace it with gitlab plugins. The problem is that I need to put the version of my project into the built application (via Webpack's DefinePlugin), but the version field of my package.json is always set to 0.0.0. I would like to be able to use semantic-release to print the version that would be published and use it in webpack DefinePlugin. Currently, the only way to do that would be to parse the output of a dry-run, but it is complicated and not stable. ## New feature description I see two ways this could happen : * The simple one is to provide a cli option to instruct semantic release to just print the version. For example `semantic-release --print-next-version` * Allow a more extensive programmatic usage of semantic-release, with a JS api that would (among other things) allow to retrieve the next version. I could open a PR for the first solution if you'd like. The second one is a bigger task (probably several tasks)

Comments (0)

No comments yet. Start the discussion.

Comment on this issue