Bug - Creating a release with current commit rules gives error
Closed this issue · 0 comments
Describe the bug
A clear and concise description of what the bug is.
When a release is being made it will ask to input the version number, after that is passed it will commit it to the branch. Since there are rules how to create a commit it won't pass.
To Reproduce
Steps to reproduce the behavior and be very detailed
- branch out
- run npm run release
- Create the version number
- See the error when it tries to commit
Expected behavior
A clear and concise description of what you expected to happen.
- Either not commit the changes and do it manually every release
- Or configure the rules to let the commit pass when a release is being mad
Screenshots
If applicable, add screenshots to help explain your problem.
Version of SDDS or which package
E.g 1.2.3 or @scania/theme-light v2.3.4
components 1.5.2
System information:
Please complete the following information, don't forget version
- Device: macbook pro
- OS: macOS
Additional context
Add any other context about the problem here.
There is a command in lerna that might work to solve this issue "lerna publish --no-git-tag-version"