Issue:
When a PR is merged to master branch it is creating a patch version bump by creating a tag. Which is not required as per release cycle followed by the development team.
Solution proposed
The reason for the same is due to configuration in GitHub action which is set to patch. The reference of configurations can be found at. Changing the default setting to none can help not creating a tag until unless there is a release planned by the respective development team.
Have proposed the same through a PR #212
Issue: When a PR is merged to
masterbranch it is creating a patch version bump by creating a tag. Which is not required as per release cycle followed by the development team.Solution proposed The reason for the same is due to configuration in GitHub action which is set to patch. The reference of configurations can be found at. Changing the default setting to
nonecan help not creating a tag until unless there is a release planned by the respective development team. Have proposed the same through a PR #212