Epic Goal

• Track items towards sha512 digest readiness in Q2 2026.

Why is this important?

• sha512 readiness is a required step toward PQ readiness which is a company goal for the not-so-distant future.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• No more hardcoded / assumed dependency on sha256. (configurable) support for sha512 (and other digests).
• Basic podman / buildah commands: pull, push, run, build and skopeo commands: sync, copy, inspect work like usual.

Dependencies (internal and external)

1. podman
2. buildah
3. skopeo
4. c/common
5. c/image
6. c/storage
7. podman-py

1. oci libraries (go-digest, distribution-spec)
2. quay
3. docker library
4. openshift

Previous Work (Optional):

1. RUN-2452

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>