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

[v5.0] Bump c/common to v0.58.2 #22386

Conversation

TomSweeneyRedHat
Copy link
Member

@TomSweeneyRedHat TomSweeneyRedHat commented Apr 15, 2024

Bumping c/common to v0.58.2 in preparation for
Podman v5.0.2

[NO NEW TESTS NEEDED]

Does this PR introduce a user-facing change?

Fixed a bug that leaked ipam entries when the network was removed. [#22034](https://github.com/containers/podman/issues/22034)
Fixed a bug which caused the rootless-netns to not be cleaned up on setup errors resulting in a weird resolv.conf missing error message later.  [#22168](https://github.com/containers/podman/issues/22168)
Fixed a bug to no longer use the rootless-netns logic in nested containers [#22218](https://github.com/containers/podman/issues/22218)

Bumping c/common to v0.58.2 in preparation for
Podman v5.0.2

[NO NEW TESTS NEEDED]

Signed-off-by: tomsweeneyredhat <[email protected]>
@openshift-ci openshift-ci bot added do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 15, 2024
@mheon
Copy link
Member

mheon commented Apr 15, 2024

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2024
Copy link
Contributor

openshift-ci bot commented Apr 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon, TomSweeneyRedHat

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:
  • OWNERS [TomSweeneyRedHat,mheon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added release-note and removed do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None labels Apr 16, 2024
@Luap99
Copy link
Member

Luap99 commented Apr 16, 2024

Added release notes to the PR description, @mheon please copy them into the release notes

@openshift-merge-bot openshift-merge-bot bot merged commit faf4548 into containers:v5.0 Apr 16, 2024
92 of 93 checks passed
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jul 16, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Jul 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants