Please make a new release for 1.34.x #5320
Comments
|
That is after we get the recent CVE fixes that are bubbling in. |
|
I am fine with that. |
Has dust been settled? :-) |
rahilarious
added a commit
to rahilarious/gentoo
that referenced
this issue
Feb 14, 2024
Masking because it isn't getting security fixes from upstream and seems like 1.34.x is more suitable for podman 5.x (yet to be released) containers/buildah#5320 Signed-off-by: Rahil Bhimjiani <me@rahil.rocks>
rahilarious
added a commit
to rahilarious/gentoo
that referenced
this issue
Feb 15, 2024
Masking because it isn't getting security fixes from upstream and seems like 1.34.x is more suitable for podman 5.x (yet to be released) containers/buildah#5320 Signed-off-by: Rahil Bhimjiani <me@rahil.rocks>
rahilarious
added a commit
to rahilarious/gentoo
that referenced
this issue
Feb 15, 2024
Masking because it isn't getting security fixes from upstream and seems like 1.34.x is more suitable for podman 5.x (yet to be released) containers/buildah#5320 Signed-off-by: Rahil Bhimjiani <me@rahil.rocks>
|
@rahilarious Once that's in, I'll need to bump the vendoring on 10 or 12 libraries, then we'll be able to spin a release. |
Perfect. Can't wait to read Podman 5's release notes. |
woohoo. High (podman)five ! |
gentoo-bot
pushed a commit
to gentoo/gentoo
that referenced
this issue
Mar 7, 2024
…lize 1.33.x) Masking because it isn't getting security fixes from upstream and seems like 1.34.x is more suitable for podman 5.x (yet to be released) containers/buildah#5320 Bug: https://bugs.gentoo.org/924456 From: #35261 Signed-off-by: Zac Medico <zmedico@gentoo.org>
gentoo-bot
pushed a commit
to gentoo/gentoo
that referenced
this issue
Mar 17, 2024
Masking because it isn't getting security fixes from upstream and seems like 1.34.x is more suitable for podman 5.x (yet to be released) containers/buildah#5320 Signed-off-by: Rahil Bhimjiani <me@rahil.rocks> Closes: #35261 Signed-off-by: Zac Medico <zmedico@gentoo.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
as Tom has mentioned things are not ready to be stable in main branch.
But as 1.34.0 is already released, shouldn't it receive same kind of treatment as 1.33.x and get mod-bumps? There are some CVEs fixes (buildkit related) in mod-bumps which are security concerns.
Or should 1.34.x users downgrade to 1.33.x?
The text was updated successfully, but these errors were encountered: