Repository navigation
Publish AWF multi-subject provenance bundle - #11342
Conversation
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
The local Step type lacks id and env fields, causing TS2339 errors that prevent the provenance test suite from running under the repository’s ts-jest configuration.
1 open issue
What changed in this PR
Publishes AWF’s existing multi-subject provenance bundle as a release asset for downstream verification. Consumer adoption remains separate; this PR does not change installer verification order or claim latency improvements.
Changes:
- Exports and uploads the attestation bundle after checksum generation and attestation.
- Adds assertions for bundle wiring, publication order, and release inclusion.
- Documents the bundle’s trust requirements and exclusion from its own checksums and subjects.
| File | Description |
|---|---|
scripts/ci/release-bootstrap-provenance.test.ts |
Adds assertions for provenance bundle publication. |
docs/releasing.md |
Documents the new asset and consumer verification requirements. |
.github/workflows/release.yml |
Copies the attestation bundle and includes it in the GitHub Release. |
Review effort: Max (auto)
| expect(steps[attest].id).toBe('attest_awf_release'); | ||
| expect(steps[bundle].env?.BUNDLE_PATH).toBe('${{ steps.attest_awf_release.outputs.bundle-path }}'); |
There was a problem hiding this comment.
Added optional id and env fields to the local Step type in 873f37d.
|
@copilot address review feedback |
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
|
⏳ Copilot review left inline comments. @copilot To proceed:
|
Documentation PreviewDocumentation has been built for this PR. To view locally:
Built from commit 83bca16 |
|
| Metric | Base | PR | Delta |
|---|---|---|---|
| Lines | 93.81% | 93.81% | ➡️ +0.00% |
| Statements | 92.36% | 92.35% | 📉 -0.01% |
| Functions | 93.02% | 93.02% | ➡️ +0.00% |
| Branches | 86.70% | 86.69% | 📉 -0.01% |
📁 Per-file Coverage Changes (2 files)
| File | Lines (Before → After) | Statements (Before → After) |
|---|---|---|
src/nvx/one-shot-process.ts |
84.0% → 81.5% (-2.47%) | 76.8% → 74.7% (-2.11%) |
src/commands/main-action.ts |
91.7% → 92.0% (+0.25%) | 91.4% → 91.7% (+0.24%) |
Coverage comparison generated by scripts/ci/compare-coverage.ts
|
🚀 Security Guard has started processing this pull request |
|
📡 Smoke OTel Tracing completed. All tracing scenarios validated. ✅
|
|
✅ Smoke Copilot BYOK completed. Copilot BYOK mode operational. 🔓
|
|
🛡️ Smoke Copilot Network Isolation confirmed the egress allowlist is enforced. ✅
|
|
✅ Build Test Suite completed successfully!
|
|
Smoke Cloud Hypervisor completed. Cloud Hypervisor + Copilot passed.
|
|
✅ Smoke Claude passed
|
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟
|
|
Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.
|
|
🔌 Smoke Services — All services reachable! ✅
|
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤
|
🏗️ Build Test Suite Results
Overall: 7/8 ecosystems passed — FAIL Java failure: .NET note: the first attempt crashed on a missing
|
|
Smoke (Copilot): PR "[WIP] Define trusted service-proxy support for LLM secret headers"
Overall: PASS —
|
|
EGRESS_RESULT allow=pass deny=pass
Overall: PASS — cc @lpcox
|
|
OTEL smoke test
|
Smoke Test: Copilot BYOK (Direct) Mode ✅Status: PASS All tests verified:
Running in direct BYOK mode (COPILOT_PROVIDER_API_KEY).
|
|
Cloud Hypervisor + Copilot smoke test
Overall: PASS
|
Chroot Version Comparison
Node.js doesn't match: the chroot reported
|
Smoke Test: Claude Engine Validation
Overall result: PASS
|
|
Smoke test:
Overall status: FAIL
|
|
Services smoke test: ✅ Redis PONG, ✅ pg_isready accepting connections, ✅ SELECT 1 → 1. Overall: PASS
|

This investigation asks whether repeated online attestation lookups can be reduced without weakening AWF’s release identity, checksum, subject, signer, issuer, or runner checks. This change publishes the release workflow’s existing multi-subject provenance bundle as an input for downstream verification.
cp "$BUNDLE_PATH" release/awf-release-provenance.sigstore.jsonlgithub/gh-aw; it must adopt bundle-based verification before installation latency can improve. This change leaves its verification order unchanged and makes no latency claim.