-
Notifications
You must be signed in to change notification settings - Fork 6
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 versioned files are up to date, omit the -next suffix #103
Conversation
Change-Id: Ic73ebf54c30cc9e9819ee912935434c5c77ca185 Signed-off-by: Nick Boldt <nboldt@redhat.com>
Change-Id: Ia4f08fb17f07cc0fe87821bdf814862f1519559c Signed-off-by: Nick Boldt <nboldt@redhat.com>
…4.0 or .1 Change-Id: If4a6dc6040095087f40b2f66a0aced534711f43b Signed-off-by: Nick Boldt <nboldt@redhat.com>
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.
When run from the 7.74.x branch (where I already pushed my changes) the job passed:
https://github.com/che-incubator/configbump/actions/runs/6226555508/job/16899641726
So the PR should be safe to merge now
Build 3.10 :: configbump_3.x/123: Console, Changes, Git Data |
Build 3.10 :: configbump_3.x/122: Console, Changes, Git Data |
Build 3.10 :: sync-to-downstream_3.x/4637: Console, Changes, Git Data |
Build 3.10 :: sync-to-downstream_3.x/4638: Console, Changes, Git Data |
Build 3.10 :: push-latest-container-to-quay_3.x/3265: Console, Changes, Git Data |
Build 3.10 :: push-latest-container-to-quay_3.x/3266: Console, Changes, Git Data |
Build 3.10 :: get-sources-rhpkg-container-build_3.x/4428: configbump : 3.x :: Build 55555726 : quay.io/devspaces/configbump-rhel8:3.10-10 |
Build 3.10 :: configbump_3.x/123: Upstream sync done; /DS_CI/sync-to-downstream_3.x/4637 triggered |
Build 3.10 :: get-sources-rhpkg-container-build_3.x/4429: configbump : 3.x :: Build 55555791 : quay.io/devspaces/configbump-rhel8:3.10-11 |
Build 3.10 :: update-digests_3.x/4312: Console, Changes, Git Data |
Build 3.10 :: configbump_3.x/122: Upstream sync done; /DS_CI/sync-to-downstream_3.x/4638 triggered |
Build 3.10 :: operator-bundle_3.x/2056: Console, Changes, Git Data |
Build 3.10 :: sync-to-downstream_3.x/4639: Console, Changes, Git Data |
Build 3.10 :: push-latest-container-to-quay_3.x/3267: Console, Changes, Git Data |
Build 3.10 :: copyIIBsToQuay/1901: Console, Changes, Git Data |
Build 3.10 :: sync-to-downstream_3.x/4639: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/4430 triggered; /job/DS_CI/job/dsc_3.x triggered; |
Build 3.10 :: operator-bundle_3.x/2056: Upstream sync done; /DS_CI/sync-to-downstream_3.x/4639 triggered |
Build 3.10 :: update-digests_3.x/4312: Detected new images: rebuild operator-bundle |
Build 3.10 :: dsc_3.x/1362: Console, Changes, Git Data |
Build 3.10 :: update-digests_3.x/4313: Console, Changes, Git Data |
Build 3.10 :: update-digests_3.x/4313: No new images detected: nothing to do! |
Build 3.10 :: dsc_3.x/1362: 3.10.0 CI |
Build 3.10 :: configbump_3.x/124: Console, Changes, Git Data |
Build 3.10 :: sync-to-downstream_3.x/4753: Console, Changes, Git Data |
Build 3.10 :: push-latest-container-to-quay_3.x/3364: Console, Changes, Git Data |
Build 3.10 :: get-sources-rhpkg-container-build_3.x/4548: configbump : 3.x :: Build 55722895 : quay.io/devspaces/configbump-rhel8:3.10-12 |
Build 3.10 :: configbump_3.x/124: Upstream sync done; /DS_CI/sync-to-downstream_3.x/4753 triggered |
Build 3.10 :: update-digests_3.x/4414: Console, Changes, Git Data |
Build 3.10 :: update-digests_3.x/4414: No new images detected: nothing to do! |
What does this PR do?
chore: make sure versioned files are up to date, omit the -next suffix
Change-Id: Ic73ebf54c30cc9e9819ee912935434c5c77ca185
Signed-off-by: Nick Boldt nboldt@redhat.com
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#21988
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:
Reviewers
Reviewers, please comment how you tested the PR when approving it.