Skip to content

Diagnose separate release signer public readback refusals - #23

Open
AyobamiH wants to merge 1 commit into
mainfrom
fix/release-public-readback-diagnostics-20261018
Open

AyobamiH wants to merge 1 commit into
mainfrom
fix/release-public-readback-diagnostics-20261018

Conversation

@AyobamiH

Copy link
Copy Markdown
Owner

Release run 39124373253 published the exact disposable release once, but the separate receipt signer refused public GitHub readback on three attempts. Attempts 2 and 3 preserved the same signed completion and made zero publication requests. The existing generic error hides the upstream status and prevents an evidence-based repair.

Return only the fixed endpoint label, numeric HTTP status, and strictly parsed numeric rate-limit/retry headers for this refusal. Preserve the existing 503/error code, reject all non-200 responses and redirects, cancel the unused body, and retain all signing, identity, freshness and permanent target-fence requirements. No upstream body, URL, arbitrary header, or credential is returned; no fallback or automatic retry is introduced.

Validation: build, 10 release-provider tests and both Wrangler dry-runs pass. New regression coverage checks repository/tag/release failures at 301/403/429/503, no signature/receipt persistence, no extra publication, no follow-up request, and discarded non-numeric headers. The current patch canary remains accepted at 74c12b4. This change is not production acceptance and does not solve the expired completion or unknown readback cause by weakening checks.

Please independently review the complete change at 7faddc1. Related: AyobamiH/donestate#193.

@AyobamiH

Copy link
Copy Markdown
Owner Author

@codex review

Please review the complete change at 7faddc1. Focus on refusal metadata bounds, upstream body/header redaction, no signature on refused readback, and unchanged freshness/target/key/identity boundaries. This is observability only; it must not re-authorise publication or turn the incomplete production run into success.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T12:00:01.409703Z 7faddc1 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 7faddc13c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

This branch has not been deployed

No deployments
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