Repository navigation
chore: prepare 0.1.1 release and merge-gate maintenance - #51
Merged
Merged
Conversation
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
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.
Prepare the verified review-execution hotfix for the v0.1.1 production rollout. Bump only package/runtime identity and health metadata from 0.1.0 to 0.1.1, collect the previously unreleased hotfix notes under the release, and temporarily close MERGE_DEPLOYMENT_AUTHORIZED for the documented single-SHA cutover.
PR50 is merged as a2b4073; its head and merge-commit CI passed. Real isolated ChatGPT acceptance passed for 2-file clean, 33-file cross-group authorization finding, and 93-file/four-distinct-PNG/two-commit reviews on the final implementation. All temporary session/Worker/D1 resources were cleaned up and TopkAPI was restored.
The trusted workflow SHA stays unchanged in this maintenance step. After protected merge and green CI, deploy the closed gate, recheck/drain merge intents, coordinate both callers and Worker to the actual merge SHA of this versioned source, validate OIDC/health/active configuration, then restore the gate through the established reviewed path. Browser/hosted-inference flags, credentials, quotas, repository policy, permissions and protection rules remain unchanged. No new inference or KMU feature merge is requested.
Validation: npm run check passed (246 tests, lint, typecheck, build), including the existing health/package-version consistency check. Full CI runs its native pinned-Codex Docker, sandbox, workerd/D1, browser, Actionlint, audit and image scan checks. Deployment and release publication follow only after protected merges and successful cutover verification.