-
Notifications
You must be signed in to change notification settings - Fork 248
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
Update CI VM Images #1773
Update CI VM Images #1773
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.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.
The beta indicator needs to go away:
FEDORA_NAME: "fedora-39β"
Signed-off-by: Chris Evich <[email protected]>
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.
okay, this should be ready now.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, renovate[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Oh!
@vrothberg hit this or something very similar in a couple of other PRs: 156 and 157 |
fdfaf97
to
0db156c
Compare
Argh! What's up with Renovate ignore it's own "Updates to this PR are blocked b/c you pushed a change" message, and force-push it's own update. Something is badly broken 😢 Edit: Possibly related discussion. |
0db156c
to
fdfaf97
Compare
Renovate docs on this topic mention renaming the PR, giving that a try to stop the force-push madness. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
@rhatdan why close, was that an accident or on purpose? |
I think this was handled in a separate PR, reopen if I am mistaken. |
I see now, it was in #1777 |
This PR contains the following updates:
20231116t174419z-f39f38d13
->20231208t193858z-f39f38d13