Skip to content

Bump c/common 0.68.0, c/image 5.40.0, c/storage 1.63.0#28791

Merged
Luap99 merged 1 commit into
podman-container-tools:mainfrom
TomSweeneyRedHat:dev/tsweeney/6.0-libs-bump
May 26, 2026
Merged

Bump c/common 0.68.0, c/image 5.40.0, c/storage 1.63.0#28791
Luap99 merged 1 commit into
podman-container-tools:mainfrom
TomSweeneyRedHat:dev/tsweeney/6.0-libs-bump

Conversation

@TomSweeneyRedHat
Copy link
Copy Markdown
Contributor

@TomSweeneyRedHat TomSweeneyRedHat commented May 26, 2026

Bump the following:

c/common to v0.68.0
c/image to v5.40.0
c/storage to v1.63.0

in preparation for Podman 6.0.

Buildah still needs to be bumped and vendored, but thought I'd get this part going while waiting for that.

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

  • Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
    commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
    the sign-off email address. See CONTRIBUTING.md
    for more information.
  • Referenced issues using Fixes: #00000 in commit message (if applicable)
  • Tests have been added/updated (or no tests are needed)
  • Documentation has been updated (or no documentation changes are needed)
  • All commits pass make validatepr (format/lint checks)
  • Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

None

@TomSweeneyRedHat TomSweeneyRedHat added the No New Tests Allow PR to proceed without adding regression tests label May 26, 2026
@TomSweeneyRedHat
Copy link
Copy Markdown
Contributor Author

@Honny1 PTAL. It looks like you recently pulled in c/storage 1.63.1 from container-lib? Is there a PR there in containers lib that we need to backport?

@TomSweeneyRedHat TomSweeneyRedHat added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 26, 2026
Comment thread go.mod Outdated
go.podman.io/image/v5 v5.39.3-0.20260519201413-7e9ee2072844
go.podman.io/common v0.68.0
go.podman.io/image/v5 v5.40.0
go.podman.io/storage v1.63.1-0.20260519201413-7e9ee2072844
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

storage is not set to v1.63.0

@Honny1
Copy link
Copy Markdown
Contributor

Honny1 commented May 26, 2026

@Honny1 PTAL. It looks like you recently pulled in c/storage 1.63.1 from container-lib? Is there a PR there in containers lib that we need to backport?

No, I don't believe we need to. I actually vendored that PR podman-container-tools/container-libs#755 in this commit 0ff6ac8.

Bump the following:

c/common to v0.68.0
c/image to v5.40.0
c/storage to v1.63.0

in preparation for Podman 6.0.

Buildah still needs to be bumped and vendored, but thought I'd get this
part going while waiting for that.

Signed-off-by: Tom Sweeney <tsweeney@redhat.com>
@TomSweeneyRedHat TomSweeneyRedHat force-pushed the dev/tsweeney/6.0-libs-bump branch from 019ba11 to 41a99a6 Compare May 26, 2026 17:00
@TomSweeneyRedHat
Copy link
Copy Markdown
Contributor Author

@Honny1 and @Luap99 Thanks! I bumped storage to 1.63.0 and have repushed.

Copy link
Copy Markdown
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Luap99 Luap99 enabled auto-merge May 26, 2026 17:25
@Luap99 Luap99 merged commit cbcd40f into podman-container-tools:main May 26, 2026
90 of 91 checks passed
@TomSweeneyRedHat TomSweeneyRedHat deleted the dev/tsweeney/6.0-libs-bump branch May 27, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. No New Tests Allow PR to proceed without adding regression tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants