Is your feature request related to a problem? Please describe.
Our current library.properties is updated manually each time a new PR is merged with main.
Describe the solution you'd like
After a PR is approved, GitHub actions[^1] should run a script to auto-increment the version number, adhering to our guidelines[^2].
This should happen after a PR is approved and before the branch is merged.
This should also check the PR for labels / branch name to figure out how to increment the value. This system shouldn't break if we have a new major rewrite to this library.
Describe alternatives you've considered
Manually doing this, we're going to miss new updates. This might make it very difficult for us to troubleshoot code in the future.
Is your feature request related to a problem? Please describe. Our current
library.propertiesis updated manually each time a new PR is merged with main.Describe the solution you'd like After a PR is approved, GitHub actions[^1] should run a script to auto-increment the version number, adhering to our guidelines[^2].
This should happen after a PR is approved and before the branch is merged.
This should also check the PR for labels / branch name to figure out how to increment the value. This system shouldn't break if we have a new major rewrite to this library.
Describe alternatives you've considered Manually doing this, we're going to miss new updates. This might make it very difficult for us to troubleshoot code in the future.
Additional context
[^1]: GitHub Actions Documentation [^2]: semantic versioning guidelines.