Repository navigation
Conversation
Quest-Claim: 25108d1b2b838c74
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed the complete patch at 1cc420e and the remaining draft check/publish entrypoints. No actionable findings.
Direction: removing changelog rewriting directly implements the planned simplification. Version/source validation and pipeline failure propagation remain, curl reports HTTP 4xx/5xx failures with their response bodies, and source editing is explicitly manual. The separate draft XML validation check remains in place.
Verification limits: GitHub-only static review. I did not execute shell checks, build drafts, or submit anything to the datatracker; reported passing checks were not independently verified.
|
No actionable comments were generated in the recent review. WalkthroughThe publishing script now validates the version and draft file, generates XML, and submits it without changing the source or changelog. Changelog headings must be updated manually. The publishing test script and draft-publishing quest materials were removed. The check recipe now runs only Merge Risk:
|
There was a problem hiding this comment.
Important
The submit is now verbatim, so the (in progress) heading the old render path used to close will be published as-is by five drafts on their next publish.
Reviewed changes
publish.shshrinks to build-and-upload —open_next_section(heading rewriting, render/write modes, atomic rename) and the 200/201caseare gone; the source issed-rewritten and piped straight tokramdown-rfc, then POSTed withcurl --fail-with-body.publish.test.sh(653 lines) is deleted —just drafts checknow runs onlycheck.sh, sopublish.shhas no test.drafts/README.mddocuments the manual changelog step — publishing no longer edits the source.- Quest completion —
quest/m1/drafts-publish-trim.mdand itsquest/m1/README.mdentry are removed; no stale references to the deleted test remain.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head fa72788.
Compared with 1cc420e. No new actionable findings. The new guard catches the existing '(in progress)' changelog headings before XML generation or submission, and the README now requires closing the current heading before uploading and opening the next one afterwards. Direction: retain the explicit manual workflow rather than reintroducing source rewriting.
Verification limits: GitHub-only static review of the update and relevant surrounding source and prior discussion. No builds, tests, deployment, or publishing operations run.
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Added an
(in progress)pre-upload guard —publish.shnow scans the source for any heading still ending in(in progress), prints the offending lines, and exits before building or submitting XML, so the five drafts that still carry## Since <name>-00 (in progress)cannot be uploaded with that suffix. - Rewrote the publish section of
drafts/README.md— it now says to close the submitted version's changelog heading before uploading and to open the next version's section only after the upload, matching the guard's ordering.
The prior review's inline concern about the verbatim upload is addressed by this guard and the README ordering, so that thread is resolved.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

Summary
sh/drafts/publish.shnow does two things: it builds the XML, rewriting-latestto the version, and uploads it to the datatracker. The changelog heading rewriting is gone.sh/drafts/publish.test.sh(653 lines) is deleted, andjust drafts checkno longer runs it.publish.shrefuses to upload while a heading still ends in(in progress), anddrafts/README.mdsays to close that heading by hand before publishing and open the next section after. This PR finishesquest/m1/drafts-publish-trim.md.Choices made without asking:
curl --fail-with-bodycall, so a non-2xx response already exits nonzero, and a mock would only test curl again.--fail-with-bodyinstead of a manualcaseon the HTTP code. The response body is still printed.Public API: none. Wire: none.
Caused by
No single PR. This removes automation that is no longer worth its cost (deletion audit).
Checks
just check: pass (exit 0). shellcheck onsh/drafts/publish.sh,quest check: pass.Models
Size: S
Implementer: Claude Code, claude-opus-5-5, low effort
Implementer: Claude Code, claude-opus-5-5, low effort (iterate, S)
(Written by Opus 5.5 with low)
🤖 Generated with Claude Code
Review
Rewritten by
quest reviewafter each round.01a1c621-2e61-7521-a6f8-cd33282275ff, round 1Source inspection found no actionable defects, but readiness remains unverified by builds or tests.