Skip to content

Fix GHCR attestation example by listing GHCR first in metadata images #40291

Closed
Closed
Fix GHCR attestation example by listing GHCR first in metadata images#40291
Labels
contentThis issue or pull request belongs to the Docs Content teamdockerPull requests that update Docker codegithub_actionsPull requests that update GitHub Actions content

Description

@LindonAliu
LindonAliu
opened on Sep 8, 2025

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/tutorials/publish-packages/publish-docker-images

What part(s) of the article would you like to see updated?

https://docs.github.com/en/actions/tutorials/publish-packages/publish-docker-images#publishing-images-to-docker-hub-and-github-packages

Why should the docs be changed? What use cases does it support?

The current order can cause the attestation to fetch a Docker Hub digest from GHCR, which returns 404. This affects users who push to multiple registries but attest only GHCR. The change prevents false failures and supports secure supply-chain workflows (SLSA-style provenance, compliance, CI reliability).

Reference failing run (context):
https://github.com/glu-lang/glu/actions/runs/17557475866/job/49865233829

Additional information

No response

Activity

  1. LindonAliu
    added
    contentThis issue or pull request belongs to the Docs Content team
    on Sep 8, 2025

  2. welcome commented on Sep 8, 2025

    @welcome
    welcomeBot
    on Sep 8, 2025 – with Welcome

    Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

  3. github-actions
    added
    triageDo not begin working on this issue until triaged by the team
    on Sep 8, 2025
  4. Sharra-writes
    added
    dockerPull requests that update Docker code
    github_actionsPull requests that update GitHub Actions content
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Sep 8, 2025

  5. github-actions commented on Nov 25, 2025

    @github-actions
    github-actionsBot
    on Nov 25, 2025 – with GitHub Actions
    Contributor

    A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

  6. github-actions
    added
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Nov 25, 2025
  7. Sharra-writes
    removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Dec 5, 2025

  8. Sharra-writes commented on Jul 20, 2026

    @Sharra-writes
    Sharra-writes
    on Jul 20, 2026
    Contributor

    It looks like we fixed this internally, so I'm going to close it.

  9. Sharra-writes
    closed this as completedon Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamdockerPull requests that update Docker codegithub_actionsPull requests that update GitHub Actions content

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions