The next major release for the semantic version action will include a number of structural changes to allow further customization and control to support a wider range of release strategies.

Up until now this action has been growing functionality by increasing the number of available configuration options, all of which are handled as conditions within the script. This has worked well up to this point, but further expansion warrants breaking the main procedure up with some abstraction. The goal is to keep this easy to understand, easy to extend, and easy to configure.

For example, adding a "last version provider" abstraction would allow multiple logical strategies to be implemented. The default implementation would use tags and work identically to how the action behaves now, but this could be replaced to pull the version from a branch name or git commit messages.

In addition, this main code of the action might be broken out into a stand-alone package, which would allow it to be run on other CI systems besides GitHub Actions and may make testing and maintenance easier.