You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the --pre-commit <script> flag supports calling an NPM script before commiting changes back to git. But as a user, I don't know what the new version number is or whether package.json has been updated with the new version already.
I see two main use-cases for the existing option:
Run an NPM script which is unrelated to the new version number
Run an NPM script which requires the new version number
For the second case, typically you want the new version number so that you can update other files.
So I propose:
passing the new version number as an argument to the --pre-commit <script>
writing a new NPM module which can be figured to parse a file which contains user-defined configuration for replacing the version number in files:
The text was updated successfully, but these errors were encountered:
uglow
changed the title
Make it easy for corp-semantic-release to updated other source files with the new version number
Make it easy for corp-semantic-release to update other source files with the new version number
Feb 23, 2017
Currently the
--pre-commit <script>
flag supports calling an NPM script before commiting changes back to git. But as a user, I don't know what the new version number is or whetherpackage.json
has been updated with the new version already.I see two main use-cases for the existing option:
For the second case, typically you want the new version number so that you can update other files.
So I propose:
--pre-commit <script>
updateVersion.yml:
package.json
The text was updated successfully, but these errors were encountered: