Repository navigation
Prepare 0.1.3 and close merge gate for coordinated rollout - #60
Merged
Merged
Conversation
This was referenced Nov 16, 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
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.
Summary
Prepare the reviewed timeout/continuation fix (#59, merge
d4e0dfefaa9a5afd77141b9a8c8994053b5bddfe) for the established immutable-pin maintenance window.Only package/lockfile, health/client metadata, changelog heading, deployment gate and its exact test expectation change. No credential, quota, repository policy, OAuth/browser flag or caller pin changes. Merging does not deploy; the closed gate is deployed only from reviewed main, followed by intent reconciliation and actual-merge-SHA pin preparation.
Evidence
After: 0.1.3 metadata is consistent, and the gate/test expectation are closed for maintenance.
npm run check: 267 tests, typecheck, lint and build passed.--timeout 60completed against the final runner: https://github.com/AppSolves/TopkAPI/actions/runs/43943597407 . Both published exact-head, non-approving COMMENT reviews.Merge Danger
Door: two-way
No migration. This commit intentionally closes merging when deployed; restore the gate only after all caller pins, Worker trust and OIDC checks match.
Blast Radius: deployment
Browser OAuth/hosted-inference flags stay disabled. Repository merge opt-in, explicit commands and protection rules are unchanged.