Skip to content
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

[release-5.31] Bump c/image to v5.31.1-dev #2431

Merged

Conversation

TomSweeneyRedHat
Copy link
Member

I managed to set main to v5.31.1-dev rather than the release-5.31 branch. I've corrected main with #2430 and this will correct the release-5.31 branch

I managed to set main to v5.31.1-dev, rather than the
release-5.31 branch.  I've corected main with
containers#2430
and this will correct the release-5.31 branch

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
@TomSweeneyRedHat TomSweeneyRedHat force-pushed the dev/tsweeney/5.31.1-dev branch from f7bc846 to 9ac505f Compare May 21, 2024 19:20
Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mtrmac mtrmac merged commit 2281641 into containers:release-5.31 May 21, 2024
9 checks passed
@mtrmac
Copy link
Collaborator

mtrmac commented May 21, 2024

Does the new c/image branch need CI automation set up? Cc: @cevich

@mtrmac
Copy link
Collaborator

mtrmac commented May 21, 2024

Never mind, the tests did run already.

@cevich
Copy link
Member

cevich commented May 22, 2024

Thanks for pinging me. Just to close the loop, it looks like we do have a Cirrus-Cron setup on this repo. So the new branch needs to be added into the rotation. I've done that, but please feel free to double-check we're not missing any other branches (or should retire any).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants