Bump to c/storage v1.54.0 then c/image to v5.31.0 and then to v5.31.1-dev #2425
Conversation
|
@mtrmac PTAL |
|
containers/storage#1924 broke API and the corresponding c/image update is not yet reviewed/merged. Looking… I guess something usually goes wrong, so let’s hope this fills our quota for this week. |
|
Just for easier finding, the c/image PR that's blocking, I believe, is #2416 |
There was a problem hiding this comment.
@TomSweeneyRedHat this would probably now compile, but please wait until #2428 gets in, at least for the TOCDigest part.
As the title says. This is readying for Podman v5.1 Signed-off-by: tomsweeneyredhat <[email protected]>
Bump back to a dev version for the main branch. Signed-off-by: tomsweeneyredhat <[email protected]>
mtrmac
force-pushed
the
dev/tsweeney/v1.54.0
branch
from
ed10067 to
ec3f0e5
Compare
There was a problem hiding this comment.
@TomSweeneyRedHat After some rebases done by GitHub, this is just a version number bump, and LGTM.
But please double-check this after me (and then merge).
|
@mtrmac Thanks, looking through it now. |
|
@mtrmac LGTM, I had to convince myself that that v1.54 bump for storage was there. |
As the title says. Bumping c/storage to v1.54.0 and then c/image to v5.31.0 and v5.31.1-dev. This is in preparation for Podman v5.1