fix(release): upload assets through the GitHub release endpoint - #59
Merged
Conversation
This was referenced Sep 11, 2026
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.
Preview run 34621647795 verified and signed all six subjects, then failed its first asset upload. The generic API route used
api.github.comand dropped the filename query. Use the pinned client'srepos.uploadReleaseAssetin preview staging, stable staging, and zero-asset stable recovery so GitHub receives the exact bytes at its release-upload endpoint.Append publication policy 3 with the exact new workflow hashes, retaining historical policies 1/2 and artifact recipe 1. Draft identity, missing-only upload, metadata/digest readback, provenance, and reservation/tag/publication ordering remain intact. Preserve the prior source's valid tag and empty draft. Pylon #485 adds the matching consumer pins.
Verification: all three inline upload regressions failed on the old route and passed after the fix; the complete publication suite passed 205 tests with no skips. Required
npm run checkpassed. Independent checkpoint review found no actionable issues. An offline probe against the exact pinned action bundle verified the upload host, filename encoding, and unchanged binary body. Required CI passed on the exact reviewed tree. Both Ubuntu and macOS evidence bundles were independently audited: 205 core tests, 28 stress tests, all 3,034 crash cuts, and the actual 16 MiB maximum passed. A corrected protected publication run remains the live release acceptance gate.Fixes #53. Follow-up to #58.
Model: GPT-6. Harness: Codex.