[CI:ALL] Bump to v5.4.0-RC2 #25160
Merged
[CI:ALL] Bump to v5.4.0-RC2 #25160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
release-note-none
approved
baude
reviewed
Jan 29, 2025
RELEASE_NOTES.md
Outdated
| @@ -1,5 +1,81 @@ | |||
| # Release Notes | |||
|
|
|||
| ## 5.4.0 | |||
| ### Features | |||
| - Initial support for artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! | |||
There was a problem hiding this comment.
you imply this is dev ... i wonder if we should explicitly say so ?
There was a problem hiding this comment.
Maybe "A preview our Podman's support for artifacts has been added..."?
baude
reviewed
Jan 29, 2025
| - Quadlet `.pod` files now support a new field, `ShmSize`, to specify the size of the pod's shared SHM ([#22915](https://github.com/containers/podman/issues/22915)). | ||
| - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--hosts-file`, to define the base file used for `/etc/hosts` in the container. | ||
| - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--no-hostname`, which disables the creation of `/etc/hostname` in the container ([#25002](https://github.com/containers/podman/issues/25002)). | ||
| - The `podman network create` command now supports a new option for `bridge` networks, `--opt mode=unmanaged`, which allows Podman to use an existing network bridge on the system without changes. |
There was a problem hiding this comment.
Yes, but we haven't cut that yet
There was a problem hiding this comment.
fair, i just wondered if we should publish the nv x.y.z minimal needed. and i imagine we can probably do the av and nv releases nowish?
baude
reviewed
Jan 29, 2025
RELEASE_NOTES.md
Outdated
| - The `podman events` command now generates events for the creation and removal of networks ([#24032](https://github.com/containers/podman/issues/24032)). | ||
|
|
||
| ### Breaking Changes | ||
| - Due to a lack of availability of hardware to test on, the Podman maintainers are no longer capable of providing full support for Podman on Intel Macs. Binaries and images will still be produced, and pull requests related to MacOS on Intel systems will still be merged, but bugs will be fixed on a best effort basis only. We welcome any potential new maintainers who would be able to assist in restoring full support. |
|
couple of light suggestions if you push again. dealers choice on acceptance and how to deal with them. thanks @mheon |
| @@ -1,5 +1,81 @@ | |||
| # Release Notes | |||
|
|
|||
| ## 5.4.0 | |||
| ### Features | |||
| - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! | |||
There was a problem hiding this comment.
@baude did add land Brent? Or should we not mention it here at the moment and note it later?
RELEASE_NOTES.md
Outdated
| ## 5.4.0 | ||
| ### Features | ||
| - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! | ||
| - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. |
There was a problem hiding this comment.
Your call, maybe add "Please reference the podman-update(1) man page for more details."
RELEASE_NOTES.md
Outdated
| ### Features | ||
| - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! | ||
| - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. | ||
| - The `--mount type=volume` option to `podman run`, `podman create`, and `podman volume create` now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). |
There was a problem hiding this comment.
Suggested change
| - The `--mount type=volume` option to `podman run`, `podman create`, and `podman volume create` now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). | |
| - The `--mount type=volume` option for the `podman run`, `podman create`, and `podman volume create` commands now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). |
RELEASE_NOTES.md
Outdated
| - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! | ||
| - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. | ||
| - The `--mount type=volume` option to `podman run`, `podman create`, and `podman volume create` now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). | ||
| - The `--userns=keep-id` option to `podman run`, `podman create`, and `podman pod create` now supports a new option, `--userns=keep-id:size=`, to configure the size of the user namespace ([#24387](https://github.com/containers/podman/issues/24837)). |
There was a problem hiding this comment.
if you take the prior comment, take it here too.
RELEASE_NOTES.md
Outdated
| - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. | ||
| - The `--mount type=volume` option to `podman run`, `podman create`, and `podman volume create` now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). | ||
| - The `--userns=keep-id` option to `podman run`, `podman create`, and `podman pod create` now supports a new option, `--userns=keep-id:size=`, to configure the size of the user namespace ([#24387](https://github.com/containers/podman/issues/24837)). | ||
| - The `podman kube play` command now supports CDI devices ([#17833](https://github.com/containers/podman/issues/17833)). |
There was a problem hiding this comment.
Suggested change
| - The `podman kube play` command now supports CDI devices ([#17833](https://github.com/containers/podman/issues/17833)). | |
| - The `podman kube play` command now supports Container Device Interface (CDI) devices ([#17833](https://github.com/containers/podman/issues/17833)). |
RELEASE_NOTES.md
Outdated
|
|
||
| ### Breaking Changes | ||
| - Due to a lack of availability of hardware to test on, the Podman maintainers are no longer capable of providing full support for Podman on Intel Macs. Binaries and machine images will still be produced, and pull requests related to MacOS on Intel systems will still be merged, but bugs will be fixed on a best effort basis only. We welcome any potential new maintainers who would be able to assist in restoring full support. | ||
| - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as a comment characters instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. |
There was a problem hiding this comment.
Suggested change
| - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as a comment characters instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. | |
| - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as a comment character instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. |
There was a problem hiding this comment.
or maybe "as comment characters". I'm going back and forth between singular and plural here.
RELEASE_NOTES.md
Outdated
|
|
||
| ### Changes | ||
| - Podman now passes container hostnames to Netavark, which will use them for any DHCP requests for the container. | ||
| - Partial pulls of `zstd:chunked` images now only happen for images that have a `RootFS.DiffID` entry in the config, and require the layer contents to match. This resolve issues with image ID ambiguity when partial pulls were enabled. |
There was a problem hiding this comment.
"in the config". Which config?
| - Fixed a bug where the `podman manifest annotate` command could panic when the `--index` option was used ([#24750](https://github.com/containers/podman/issues/24750)). | ||
| - Fixed a bug where a Quadlet container reusing another container's network could cause errors if the second container was not already running. | ||
| - Fixed a bug where Quadlet files containing lines with a trailing backslash could cause an infinite loop during parsing ([#24810](https://github.com/containers/podman/issues/24810)). | ||
| - Fixed a bug where Quadlet would, when run as a non-root user, not generate for files in subfolders of `/etc/containers/systemd/users/` ([#24783](https://github.com/containers/podman/issues/24783)). |
There was a problem hiding this comment.
I'm not sure what "for files" is here.
|
A few suggestions for consideration, otherwise LGTM |
Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matt Heon <[email protected]>
Signed-off-by: Matt Heon <[email protected]>
|
@containers/podman-maintainers This should be ready |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, mheon 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 |
openshift-merge-bot
bot
merged commit c13ef17
into
containers:v5.4
85 of 87 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now including full release notes
Does this PR introduce a user-facing change?