Update vendor of containers/storage

[rhatdan]

No description provided.

[rhatdan]

@mtrmac not sure what is breaking here?

[flouthoc]

I think this should be version as listed below and maybe followed by go mod tidy

Suggested change

	github.com/containers/storage 4a3a3019d7659029f50c913c40e0bd94fc9ba284
	github.com/containers/storage v1.48.1-0.20230721123825-4a3a3019d765

[rhatdan]

FIxed

[mtrmac]

Is there a specific reason to update, on the main brach, to an unreleased version?

To be clear, I’m not at all saying that this is undesirable, I’m just curious what is the context is. Are some new users of the new features coming?

[rhatdan]

I am trying to roll everything forward, in order to get continuous testing and updates via renovate,

[rhatdan]

There seems to be something that is locking Podman to the released version of containers/image and make vendor keeps pushing it back.

[mtrmac]

There seems to be something that is locking Podman to the released version of containers/image and make vendor keeps pushing it back.

That’s because the last released version of c/image is on a branch. The fix for that is, IIRC:

• In c/image, merge the release-5.26 branch into main (so that main is visible in Git as a successor to the last released version)
• In a consumer, update c/image at least to that merge point.

See #1842 and containers/skopeo#1911 .