chore(blog): add live ws migration

[NathanFlurry]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-site	Building	Preview	Comment	Nov 24, 2025 8:59am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Nov 24, 2025 8:59am
rivet-inspector	Ignored	Preview		Nov 24, 2025 8:59am
rivetkit-serverless	Skipped			Nov 24, 2025 8:59am

[NathanFlurry]

• chore(blog): add live ws migration #3536 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: chore(blog): add live ws migration

This PR adds a blog post introducing the Live WebSocket Migration and Hibernation feature. Overall, this is well-written documentation with clear code examples.

✅ What looks good

1. Well-structured content: The post follows a logical flow - problem statement, solution overview, and code examples
2. Consistent metadata: The frontmatter follows the existing blog post pattern with author, published date, category, and keywords
3. Comprehensive code examples: Both the Actions & Events API and low-level WebSocket API are covered with clear Actor + Client code pairs
4. Proper documentation links: Links to relevant docs pages at the end of each section

📝 Suggestions (non-blocking)

1. Line 10 - W3C compliance claim: The claim "This is fully W3C compliant" could benefit from a brief clarification of what aspect is W3C compliant (e.g., the WebSocket protocol itself, the API surface). This helps readers understand the scope of compatibility.

2. Code example consistency: In the Actions & Events API example (line 60), c.conn.state.username is set but there's no TypeScript interface defining the connection state type. For educational purposes, adding something like:

   interface ConnState {
     username?: string;
   }

   Would help readers understand the connection state typing pattern.

3. Error handling in examples: The low-level WebSocket example (lines 143-158) uses JSON.parse() without error handling. While this is fine for a blog post demonstrating the feature, a note about production error handling could be helpful for readers who copy this code.

4. Missing export for actor: Both code examples define const chatRoom = actor({...}) but don't show the export statement. It might be helpful to add export default chatRoom; or show how this integrates with the registry mentioned in the client code.

✅ Verification

• Image file (image.png) is included in the directory
• MDX syntax appears correct for the website's CodeGroup component
• File naming convention matches existing posts pattern

Verdict: This PR looks good to merge. The content is clear, technically accurate, and follows the existing blog post conventions. The suggestions above are minor polish items that could be addressed in a follow-up if desired.

[graphite-app]

Merge activity

• Nov 24, 9:13 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Nov 24, 9:13 AM UTC: CI is running for this pull request on a draft pull request (#3537) due to your merge queue CI optimization settings.
• Nov 24, 9:14 AM UTC: Merged by the Graphite merge queue via draft PR: #3537.