yakovlev-alexey / bump-package-version-action Goto Github PK

Add support for release candidates (RC versions)

Currently I don't have a great understanding how RC versions should get calculated from commit messages. Perhaps commits to a certain branch (e.g. release) should create a RC. Needs research and feedback from users having applications of release candidate versions.

Currently ties to npm are very loose. Perhaps there is a possibility to replace the code using npm version with a plugin. This would allow using this action for basically any package manager, not only NodeJS ones (or even without one).

However there is a big question - how to actually insert plugins into an action? Needs researching

Add tag-prefix input that allows to specify prefixes such as v or no prefix.

Use this prefix for commit messages. Remove v prefix that npm return when specifying current version. Separately output version and tag (version is always without v, tag is with the specified prefix`.

Currently only commit messages are checked for matches. But according to conventional commits you should be able to write BREAKING CHANGES in commit body for a major version bump.