Manifest not displayed in GHCR UI when using attestations

There is no problem with this:

No problem

- name: Push Docker image
  uses: docker/build-push-action@2eb1c1961a95fc15694676618e422e8ba1d63825
  with:
    context: src
    tags: ${{ needs.metadata.outputs.tags }}
    labels: ${{ needs.metadata.outputs.labels }}
    cache-from: type=gha
    cache-to: type=gha,mode=max
    load: true
- name: Push Docker image to GHCR
    run: docker push -a ghcr.io/${{ inputs.image-name }}

But a problem with this:

Breaks

- name: Push Docker image
  uses: docker/build-push-action@2eb1c1961a95fc15694676618e422e8ba1d63825
  with:
    context: src
    tags: ${{ needs.metadata.outputs.tags }}
    labels: ${{ needs.metadata.outputs.labels }}
    cache-from: type=gha
    cache-to: type=gha,mode=max
    push: true

Is this a GHCR problem or a problem with the action?

Expected behaviour (First code snippet)

Actual behaviour (Second code snippet)

As you can see some weird unknown/unknown architecture appears and GHCR can no longer read labels including license and description.

Logs

First log: https://pastebin.com/xVnafXKJ
Second log: https://pastebin.com/X4yyB9gx

Start with the two workflow snippets and compare the linked first and second logs, focusing on the differing load and push settings and the resulting manifest. Reproduce the behavior with attestations and verify that the GHCR UI shows the expected architecture, labels, license, and description without an unknown/unknown entry.