Closed KonradBkd closed 6 days ago
We should add version bump as the last step of a successful delivery. We could even automate the PR creation. I'll create an internal issue for this.
We should add version bump as the last step of a successful delivery. We could even automate the PR creation. I'll create an internal issue for this.
I second this. should be easy enough to automate
We should add version bump as the last step of a successful delivery. We could even automate the PR creation. I'll create an internal issue for this.
I second this. should be easy enough to automate
Downside is that we have to guess that the next version is a Patch increment. If a some other increment happens, we have to adjust. Looking back, this is not a real problem though.
We should add version bump as the last step of a successful delivery. We could even automate the PR creation. I'll create an internal issue for this.
I second this. should be easy enough to automate
Downside is that we have to guess that the next version is a Patch increment. If a some other increment happens, we have to adjust. Looking back, this is not a real problem though.
We could also put the bump into a separate workflow_dispatch
workflow, which can be parametrized with an option to select the kind of bump. This workflow would be able to see the same secrets as the tagging workflow.
Bump SilKitVersion.cmake + Changelog to 4.0.55