Version Packages#714
Conversation
Deploying stackflow-demo with
|
| Latest commit: |
92bc4b3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d0bc17a1.stackflow-demo.pages.dev |
| Branch Preview URL: | https://changeset-release-main.stackflow-demo.pages.dev |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR releases patch version 1.11.1 for ChangesRelease Documentation and Version Update
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
stackflow-docs | 92bc4b3 | Commit Preview URL | Jun 01 2026, 12:42 PM |
ENvironmentSet
left a comment
There was a problem hiding this comment.
Release verified: @stackflow/plugin-history-sync@1.11.1 (SSR hydration fix). Required CI (build/typecheck/test/changesets) green.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@stackflow/plugin-history-sync@1.11.1
Patch Changes
b7724e9: Fix an SSR hydration mismatch that occurred when an activity declared a non-empty
defaultHistory.The staged
defaultHistorysetup navigation was kicked off synchronously inside theonInithook, which runs during the first client render. As a result, the client's first render contained more activities than the server-rendered output, producing a React hydration mismatch.The setup navigation is now kicked off from a post-commit effect instead, so the server and the client's first render produce identical output (eliminating the mismatch) while the staged "stacking" setup animation still plays after hydration.