Skip to content

upstreaming: verified native artifact compatibility fix for gh-aw v1.2.2 - #4940

Merged
luhenry merged 2 commits into
mainfrom
upstreaming-pipeline
Nov 18, 2026
Merged

luhenry merged 2 commits into
mainfrom
upstreaming-pipeline

Conversation

@luhenry

@luhenry luhenry commented Nov 18, 2026

Copy link
Copy Markdown
Member

Fix the native artifact delivery blocker observed in investigator run 44415024119. The operator approved this compatibility patch.

Authorization change

The native artifact handler now wraps its upload in the existing protected native-target frame (withClaimResourceEffects). Immutable Work cannot predict a future worker run ID at admission. The frame still enforces the immutable repository selector and exact original Claim/dispatch/run binding before any upload.

Unchanged: durable Completion, original Claim and factory fences, repository-ID checks, closed channels, private in-process delivery receipts, independent artifact ID/name/run/digest/size readback, and verified Result checks. No scheduler change or generic-artifact fallback.

Installation

  • Stay on pinned gh-aw v1.2.2.
  • Use supported jobs.safe_outputs.pre-steps to check out trusted patch code at the exact workflow SHA.
  • Check the original handler SHA-256, apply the patch, then check the complete resulting SHA-256. Unknown input fails closed.
  • Regenerate lock files, never edit generated workflows by hand.

Companion integration corrections

  • v1.2.2 emits validating replay JSON on stderr; accept one complete projection only after a successful exit.
  • Native artifact uploads accept path, not a name override. Require the actual claim-<hash>-upstreaming-out artifact name, retaining exact ID/digest/run verification.

Validation

  • 125 pipeline tests pass.
  • 109 native regressions pass against the pinned source (30 artifact-handler tests and 79 resource-scope tests). Tests include rejection of foreign runs, repository IDs and Claims, cancelled Claims, reused factories, closed channels and altered artifact metadata. All uploads/APIs are mocked.
  • gh-aw v1.2.2 compile and lock checks pass.
  • State-only pushes trigger no workflows.

Live publication has not yet been established. The old failed Work retains its pending delivery barrier and is not treated as verified.

All modifications to contribution forks must be made exclusively by upstreaming workflows in this control repository. This PR does not directly modify or dispatch CI in any contribution fork.

Use the existing protected native-target frame around artifact uploads. Preserve immutable repository selectors, original Claim/run binding, Completion, closed channels and independent artifact verification. Add native-handler regressions and fail-closed installer tests. Read replay JSON from its actual CLI stream and require the native artifact name.
…ed handlers

Use supported safe_outputs pre-steps at the exact workflow revision. Keep v1.2.2 pins and regenerate locks. Run native handler and resource-scope regressions in validation.
@luhenry
luhenry merged commit 101ad75 into main Nov 18, 2026
4 checks passed
@luhenry
luhenry deleted the upstreaming-pipeline branch November 18, 2026 23:24
@luhenry luhenry mentioned this pull request Nov 18, 2026
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