fix: verify Windows release artifact namespace - #264
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough릴리스 아티팩트 검증이 플랫폼별 디렉터리 범위로 제한됩니다. Changes릴리스 아티팩트 검증
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The PR corrects Windows release-artifact namespace validation and adds regression coverage without changing release authority; no actionable merge-blocking risk remains beyond normal checks and review. Sequence Diagram(s)sequenceDiagram
participant attest-release
participant verify-release-artifacts.sh
participant release-artifacts
participant SBOMGeneration
attest-release->>verify-release-artifacts.sh: 다운로드한 아티팩트 검증
verify-release-artifacts.sh->>release-artifacts: 플랫폼별 디렉터리와 파일 확인
release-artifacts-->>verify-release-artifacts.sh: 검증 결과 반환
alt 검증 성공
verify-release-artifacts.sh-->>attest-release: 성공 상태 반환
attest-release->>SBOMGeneration: SBOM 생성 진행
else 검증 실패
verify-release-artifacts.sh-->>attest-release: 실패 상태 반환
attest-release-->>SBOMGeneration: 후속 단계 중단
end
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 7 functions across 3 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Pull request was converted to draft
Pull request was converted to draft
Pull request was converted to draft
Pull request was converted to draft
Pull request was converted to draft
Pull request was converted to draft
Purpose
Repair the PR-executable release artifact verifier after the merged
actions/download-artifactv8 compatibility line exposed an exact platform-namespace mismatch.Exact failure and root cause
On PR #214 exact head
a6cfd32e1c56ea12bddcfdd3f5caff9d6f95e9f6, Release run32936765719built and uploaded Linux, Windows, and macOS artifact sets successfully. Thedownload-artifact-pr-compatjob98083412428downloaded the v8 artifact family successfully and then failed only inVerify downloaded release artifact contract.The release matrix uploads artifacts under
release-disksage-${{ matrix.os }}-${{ github.run_attempt }}and the Windows matrix key iswindows-2022. The verifier instead requiredrelease-disksage-windows-latest-${run_attempt}, so a correct downloaded artifact set could never satisfy the directory contract.Test-first repair
ubuntu-22.04,windows-2022,macos-latest) and executes the source-controlled Bash verifier..github/scripts/verify-release-artifacts.shfromwindows-latesttowindows-2022.The verifier's exact file cardinality, bundle types, six operational CLI artifacts, six adjacent SHA-256 records, checksum validation, non-regular-path rejection, and read-only PR compatibility authority remain unchanged.
Authority boundary
This adds no tag, release-publication, package-publication, attestation, secret, or write authority to pull requests. It only repairs the read-only compatibility proof already introduced by the merged #230 line.
Addresses #242.
Required before integration
Keep Draft until the unchanged exact head proves the real
download-artifact-pr-compatjob succeeds on the downloaded Linux/Windows/macOS release artifacts, all applicable current Test/Release/Security/SAST and central required workflows are terminal-success, current valid findings are addressed, live review/ruleset requirements are satisfied, and repository-wide exact production coverage requirements are not weakened. Pending, skipped-required, failed, stale, predecessor, status-only, or synthetic evidence is non-passing.Summary by CodeRabbit
개선 사항
테스트