Skip to content

Preserve release attestations in registry ingest#68

Merged
gontzess merged 1 commit intomainfrom
gontzess/preserve-registry-attestations
Apr 27, 2026
Merged

Preserve release attestations in registry ingest#68
gontzess merged 1 commit intomainfrom
gontzess/preserve-registry-attestations

Conversation

@gontzess
Copy link
Copy Markdown
Contributor

Why

Release manifests already include per-asset provenance and SBOM attestations plus an image attestation summary, but record-release dropped those fields before calling the registry API. Exported stable manifests could therefore lose verification metadata even when the per-version manifest and Sigstore bundles existed.

What this changes

This keeps per-asset attestation descriptors in the registry request and maps the manifest-level image attestation summary onto each image record, matching the connector-registry importer and exporter model. Asset attestation summaries remain derived from per-asset entries; image attestations remain OCI-referrer based, so their bundle URL may be empty.

Tests cover asset attestation preservation, incomplete asset entries, image attestation fan-out, and the JSON request shape.

@gontzess gontzess marked this pull request as ready for review April 27, 2026 19:22
@gontzess gontzess merged commit b80b12b into main Apr 27, 2026
1 check passed
@gontzess gontzess deleted the gontzess/preserve-registry-attestations branch April 27, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants