Bump c/storage to v1.52.0, c/image to v5.30.0 and then v5.30.1-dev #2249
Conversation
There was a problem hiding this comment.
@TomSweeneyRedHat IIRC we actually want a feature backport, so this shouldn’t go ahead, should it?
(Also, the tests fail.)
|
@mtrmac Urvashi added some changes to c/image main that she needed for the Farm Build work. The thinking was to bump the version here and in c/storage, then bump those versions in the c/common v0.57.0 branch which went out with Podman v4.8, then create a new c/common there in that branch and merge all into the Podman v4.9 branch. I had initially planned to also bump c/common, but apparently there are some non-compatible Podman v5.0 changes in c/common main. I was hoping this approach would be less intensive than backporting to the c/storage and c/image repos. However, if you or others think there are changes in here or c/storage that would be incomptatible with Podman v4.9, backports will have to be done instead. I tell you, whitespace issues will be the death of me yet. |
As thet title says, bumping to v5.30.0 in preparation of Podman v4.9 [NO NEW TESTS NEEDED] Signed-off-by: TomSweeneyRedHat <[email protected]>
As the title says. Bumping main to v5.30.1-dev [NO NEW TESTS NEEDED] Signed-off-by: TomSweeneyRedHat <[email protected]>
TomSweeneyRedHat
force-pushed
the
dev/tsweeney/5.30
branch
from
0cc1842
to
57e4f67
Compare
|
UGH! Closing. I managed to wipe out the c/storage bump commit when fixing the whitespace. Will spin a new PR. |
|
I have already merged a bot-created c/storage bump; I apologize about the confusion that created. |
As the title says. Reading for Podman v4.9 release
[NO NEW TESTS NEEDED]