Repository navigation
Fix Hub landing feedback retries and qualify release tooling - #191
Merged
sarthakagrawal927 merged 1 commit intoOct 23, 2026
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.
The public Hub landing retains feedback drafts and consent after a lost response and retries the same submission ID. Backport only the reviewed controller into its existing v0.1.13 template and regenerate the Worker HTML/assets through the normal landing emitter; theme and all surrounding template bytes are retained.
Patch the existing backend release tooling required by security checks (Wrangler4.152.0, compatible Vitest plugin1.4.7, Vitest4.1.12 and Worker types5.20261019.1; Vite8.3.5/source-map-js1.2.2). Keep native npm backend and pnpm landing lockfiles separate. Regenerate Wrangler declaration metadata and asset module types; runtime bindings are unchanged. Both audits are clear. No private Hub/auth/sync/native data authority, schema, provider settings or Live/Journal ownership changes.
Validation: independent frozen backend/landing installs; Worker type generation/check, TypeScript, Vitest and deployment dry run; Astro check/build and normal generated snapshot; compiled390/768/1440 interrupted retry/reset/new-intent/consent checks pass with six screenshots reviewed, exact sampled live styles and no errors/overflow. Generated HTML matches the compiled landing after the existing public-origin placeholder substitutions. Native Swift CI remains a merge gate.