Skip to content

[publish] Verify package-archive SHA-256 against package job output - #212

Draft
mosuem wants to merge 1 commit into
publish-attest-inputfrom
publish-verify-archive-digest
Draft

mosuem wants to merge 1 commit into
publish-attest-inputfrom
publish-verify-archive-digest

Conversation

@mosuem

@mosuem mosuem commented Nov 13, 2026

Copy link
Copy Markdown
Member

Note

This PR was generated by an AI coding agent (Jetski) on behalf of @mosuem.

Stacked on #210.

Passes the SHA-256 digest of $RUNNER_TEMP/package.tar.gz out of the package job via a job output (archive-sha256) and verifies the downloaded package-archive artifact against it in both attest and publish before signing or publishing.

Why

All jobs in the same workflow run (including sibling jobs in the calling workflow, even ones running on self-hosted runners) share ACTIONS_RUNTIME_TOKEN and can overwrite workflow artifacts via the Actions artifact service. Job outputs, by contrast, are isolated per job in the GitHub Actions control plane, so verifying needs.package.outputs.archive-sha256 guarantees attest and publish only consume the exact archive built by package.

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.

1 participant