Closed yuetloo closed 3 years ago
The error was `not in a git directory` [https://github.com/aragon/ui/runs/2746409141?check_suite_focus=true](https://github.com/aragon/ui/runs/2746409141?check_suite_focus=true)
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for contributing to Aragon! 🦅
Please review the code and understand how merge-release updates npm version. Npm version are triggered by certain commit messages, i.e. "feat:" will trigger minor version bump, "BREAKING CHANGE" will trigger major version bump, all other will trigger patch version change. @Rekard0 - v2 branch will need "BREAKING CHNAGE" in your commit message to trigger major version change...
https://github.com/mikeal/merge-release#workflow
Also, it wont' update package.json (version), only the tag will have the proper version in the package.json file. See here: https://github.com/mikeal/merge-release/issues/12#issuecomment-571252655
I don't think this workflow was ever used to publish npm package as the actions failed for more than 9 months.