Skip to content

chore(site): weekly changelog 2026-06#4141

Open
NathanFlurry wants to merge 1 commit intomainfrom
changelog-2026-06
Open

chore(site): weekly changelog 2026-06#4141
NathanFlurry wants to merge 1 commit intomainfrom
changelog-2026-06

Conversation

@NathanFlurry
Copy link
Member

Weekly changelog for February 5, 2026.

Changes

  • Namespace & Project Archive - Archive resources from dashboard (#4126)
  • OpenCode Support - Sandbox Agent now supports OpenCode adapter
  • ARM Builds - Native ARM64 Docker images for Sandbox Agent
  • Embedded UI - UI bundled into Sandbox Agent binary
  • GitHub Preview CI - Improved preview deployment workflow

@railway-app
Copy link

railway-app bot commented Feb 6, 2026

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

Service Status Web Updated (UTC)
website ❌ Build Failed (View Logs) Web Feb 6, 2026 at 11:10 pm
mcp-hub ✅ Success (View Logs) Web Feb 6, 2026 at 11:09 pm
frontend-cloud 😴 Sleeping (View Logs) Web Feb 6, 2026 at 3:28 am
frontend-inspector 😴 Sleeping (View Logs) Web Feb 6, 2026 at 3:25 am

@claude
Copy link

claude bot commented Feb 6, 2026

PR Review - Weekly Changelog 2026-06

Summary

This PR adds the weekly changelog for February 5, 2026, adds frontmatter to two documentation pages, and temporarily disables typecheck for code blocks in Astro config. The changes are straightforward and mostly positive.


✅ Positive Aspects

  1. Proper Frontmatter Addition: The documentation pages appearance.mdx and lifecycle.mdx now have the required frontmatter fields (title, description, skill) as specified in CLAUDE.md, which ensures they render correctly in the sitemap.

  2. Consistent Changelog Format: The new weekly update follows the established pattern from previous changelog posts with proper frontmatter and structure.

  3. Good Content Organization: The changelog is well-organized by section (Rivet Cloud, Sandbox Agent, CI/CD) with clear subsections.


⚠️ Issues & Concerns

1. Astro Config Change Should Not Be Committed

File: website/astro.config.mjs:32

- typecheckCodeBlocks(),
+ // typecheckCodeBlocks(), // Temporarily disabled for local dev

This appears to be a local development workaround that was accidentally committed. This should be reverted before merging. Disabling type checking for code blocks defeats the purpose of the type checking system mentioned in the blog post "Type Check Your Docs: The Agents Are Suffering".

Recommendation: Revert this change or investigate why type checking is causing issues locally and fix the root cause.

2. Inconsistent Formatting in Changelog

File: website/src/content/posts/2026-02-05-weekly-updates/page.mdx:13-14

There's an inconsistency in the section headers:

### Namespace & Project Archive
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

The "Sandbox Agent" section uses ## (h2) while "Namespace & Project Archive" uses ### (h3). Looking at previous changelog posts like 2026-01-30-weekly-updates, the pattern should be:

  • ## for major sections (Rivet Core, Sandbox Agent, etc.)
  • - for bullet points within sections

Recommendation: Either:

  • Change line 14 from ## Sandbox Agent to use consistent heading level, OR
  • Restructure to match the format in 2026-01-30-weekly-updates/page.mdx which uses h2 for major sections and bullet lists for items

3. Unclear/Confusing Content

File: website/src/content/posts/2026-02-05-weekly-updates/page.mdx:19-20

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

This content is confusing:

  • What is Gigacode exactly? The description is circular ("allows you to use OpenCode UI").
  • Why mention "This isn't a fork of Opencode" - this feels defensive and doesn't add clarity.
  • The relationship between Gigacode, OpenCode, and Sandbox Agent SDK is unclear.

Recommendation: Rewrite for clarity. For example:

### Gigacode Launch for Sandbox Agent SDK
Gigacode provides a web-based UI for interacting with any coding agent through the Sandbox Agent SDK, leveraging OpenCode's interface while remaining a standalone implementation.

4. Empty Line in Content

File: website/src/content/posts/2026-02-05-weekly-updates/page.mdx:21-22

There's an unnecessary double blank line between "Gigacode Launch" and "ARM Builds" sections.

Recommendation: Remove one blank line to maintain consistency.


📝 Style & Convention Notes

According to CLAUDE.md requirements for blog posts, all required frontmatter fields are present:

  • title
  • description
  • author (valid: nicholas-kissel)
  • published (date string)
  • category (valid: changelog)
  • keywords (optional, but present)

🔒 Security & Performance

No security concerns identified. The changes are content-only with no code execution paths.


🧪 Test Coverage

N/A - Documentation and content changes don't require additional test coverage.


📋 Action Items

Before merging:

  1. CRITICAL: Revert the typecheckCodeBlocks() comment in astro.config.mjs or fix the underlying issue
  2. RECOMMENDED: Fix heading level inconsistency in the changelog
  3. RECOMMENDED: Clarify the Gigacode description
  4. MINOR: Remove extra blank line at line 21-22

Overall Assessment

The core content additions (frontmatter for docs, changelog content) are good, but the Astro config change is a blocker that should not be merged in its current state. The content issues are minor but would improve clarity if addressed.

Verdict: ⚠️ Changes Requested - primarily due to the Astro config change

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 6, 2026

More templates

@rivetkit/cloudflare-workers

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

@rivetkit/db

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/traces

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

@rivetkit/workflow-engine

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

@rivetkit/virtual-websocket

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

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: 3d1ce9c

Copy link
Member

NicholasKissel commented Feb 6, 2026


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants