Isolate release attestation credentials - #10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
結果\n- 使用已在 Resource Scheduler 正式發行驗證過的本機 RepoDigests 讀回 registry digest\n- 將 attestation 的 HOME 與 Docker config 放入本次 run 專屬目錄，不碰 runner 原本的 HOME，也不覆蓋 Buildx builder config\n- 清理時分別登出並移除 run-owned attestation HOME，再以原 builder config 移除 builder\n- digest 不符時輸出明確失敗原因，不再只留下 exit 1\n\n## 失敗證據\n兩次 v3.1.5 恢復工作都在 image push 成功、GHCR 回報相同 digest sha256:ef30f156526ccda150f4b174b29f113fc093c1eb0af277a460493cdbd7385a24 後，才於同一 Publish step 的靜默 credential/assertion 區段失敗；建置、測試、SBOM 與 Trivy 均成功。\n\n## 本機驗證\n- workflow YAML parse\n- git diff --check\n- �ash -n scripts/check-source-gates\n- 所有非 Git worktree 來源閘門 fixture 通過；Linux CI 負責完整權威驗證