fix: preserve prefetched page hydration and release 3.1.0 - #276
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 70d318bbea
ℹ️ 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".
olliethedev
changed the title
olliethedev
changed the title
This branch was successfully deployed
1 participant
Unchanged provider inputs could publish new context values during hydration, replacing prefetched blog HTML with a skeleton while its lazy page module was loading. Memoize Stack/Auth/router context values and generate stable provider overrides for Next.js, React Router, and TanStack Start. Existing
route.PageComponentrendering, eager authorization, and page code splitting remain intact. Optional direct guarded blog entries reuse the same permissions and error behavior.Promote the verified RC runtime to stable
@btst/[email protected]and@btst/[email protected]. Generated installations pin the matching stack and@btst/[email protected]; its session-subscription fix prevents unrelated configuration updates. Extend npm availability verification to 15 minutes to accommodate publish-time scanning observed during the RC release.RC validation: 1,061 stack tests plus CLI tests, typecheck, lint, Knip, docs build, strict npm/pnpm packed consumers, registry validation and both deployment previews passed. Full generated-app suites passed: Next.js 191 tests, React Router 186, TanStack Start 188; a TanStack-only case is skipped in the other two frameworks. Dedicated regressions cover hydration continuity, immediate authorization revocation, current callbacks, failed module loading and page bundle separation.
A deployed consumer using the published RC passed cold anonymous list/post checks with JavaScript delayed 1.5 seconds. Content stayed visible after its first reveal, with no browser errors or unrelated page implementations, and theme changes worked. That integration combines stable overrides, the companion Auth UI and a version-pinned next-themes correction. Brief initial streaming placeholders remain; meaningful identity/runtime/context changes can still reveal loading while code or data is unavailable.
Stable candidate
c064e752passed final CI, all three framework browser suites, both Vercel deployments, independent final-head review and the release gate. Merged into main; BTST 3.1.0 is published. The release workflow passed, and npmlatest, source commit and integrity were verified for stack 3.1.0, codegen 3.1.0 and companion Auth UI 2.0.1.