-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: make sure that version bumping happens everytime #1090
chore: make sure that version bumping happens everytime #1090
Conversation
This cannot be merged until the step is removed. |
… care of patch and release branches get bumped too via minor
bc905d6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm (even though I have to admit that this whole generate-version scripts/programs are really confusing)
Understood. If you could let me know how we can improve them, please tell me straight away. I will try to simplify as much as possible but currently my PRs are focusing on only "touching up" without rewriting |
I created an issue #1094. Although I agree, that this has no priority. |
What this PR does / why we need it
This makes sure that we dont only do a patch bump on main after a successful branch cut, but we also do a bump on the release branch (for the next z / patch version) after the minor has been released.
Creates a shared workflow that can be called from other workflows.
Which issue(s) this PR fixes
Ensures more automated workflows after the rework from #995
Example run at https://github.com/open-component-model/ocm-cicd-playground/actions/runs/11838213132/job/32986884073