chore(site): weekly changelog

[NicholasKissel]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[NicholasKissel]

• chore(site): weekly changelog #4152 👈 (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.

[railway-app]

🚅 Deployed to the rivet-pr-4152 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 16, 2026 at 9:58 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 16, 2026 at 9:48 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 6, 2026 at 11:20 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 6, 2026 at 11:20 pm

[claude]

Pull Request Review

Summary: This PR adds a weekly changelog post for 2026-02-05, documenting various updates to Rivet Cloud, Sandbox Agent, and CI/CD improvements.

---

✅ Positive Observations

1. Correct frontmatter structure - All required fields are present (author, published, category, keywords, title, description)
2. Valid author - nicholas-kissel is in the allowed author enum
3. Valid category - changelog is a valid category
4. Good keyword selection - Keywords are descriptive and relevant

---

⚠️ Issues Found

1. Inconsistent formatting with previous weekly updates

The content structure doesn't match the established pattern from recent weekly changelogs. Compare:

2026-01-30 format (correct):

## Rivet Core
- Swift SDK for native iOS/macOS development with RivetKit
- Vercel-flavored examples for seamless deployment

This PR's format:

## Rivet Cloud

### Namespace & Project Archive
Projects and namespaces can now be archived...

The new format uses H3 headings with detailed descriptions, while the established pattern uses bullet points. For consistency, this should follow the bullet-point format.

2. Missing blank line (website/src/content/posts/2026-02-05-weekly-updates/page.mdx:13-14)

There's a missing blank line between sections:

Projects and namespaces can now be archived directly from the dashboard. Archived resources are hidden from the default view but can be restored at any time.
## Sandbox Agent

Should be:

Projects and namespaces can now be archived directly from the dashboard. Archived resources are hidden from the default view but can be restored at any time.

## Sandbox Agent

3. Extra blank line (website/src/content/posts/2026-02-05-weekly-updates/page.mdx:21-22)

There's an unnecessary double blank line:

Gigacode allows you to use OpenCode UI with any coding agent, built into Sandbox Agent SDK. This isn't a fork of Opencode.


### ARM Builds

Should have only one blank line between sections.

4. Inconsistent capitalization

"Opencode" vs "OpenCode" - line 20 uses "Opencode" but line 17 correctly uses "OpenCode". Should be consistent.

---

📝 Recommendations

1. Reformat to match established pattern - Use bullet points instead of H3 subheadings with descriptions for better consistency across weekly updates
2. Fix spacing issues - Add missing blank line after line 13, remove extra blank line after line 21
3. Fix capitalization - Change "Opencode" to "OpenCode" on line 20

---

🔍 Code Quality: Good

• Frontmatter is properly structured
• Content is informative and well-written
• No security concerns
• No performance issues (static content)

✅ Approval Status

Approve with minor changes recommended - The spacing and formatting issues are minor and don't block merging, but addressing them would improve consistency with existing changelogs.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• custom-serverless-vercel
• example-elysia
• example-elysia-vercel
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-hono-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• example-sqlite-raw-vercel
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc
• example-trpc-vercel

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4152

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4152

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4152

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4152

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4152

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4152

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4152

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4152

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4152

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4152

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4152

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4152

commit: 52067d2