-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: CE-882 versioning on prod releasesv2 #668
Conversation
id: bump_version | ||
run: | | ||
latest_tag="${{ steps.latest_tag.outputs.latest_tag }}" | ||
# Extract major, minor, and patch versions |
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.
I don't think yml file supports comment inside a block scalar
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.
Good catch!
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.
@barrfalk LGTM. I just wonder about "#" inside run
block (there're 5 of them), it may not understand that it's a comment and run the command, but not a big deal.
We might consider updating version when merging hotfix branch to main as well.
Quality Gate passedIssues Measures |
Description
A tag is created when a release branch is created.
Merging into a release branch will increment the patch number of a version.
Merging into main will create a github release.
Fixes # (issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist
Further comments
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: