chore: deploy patch

[MasterPtato]

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

[railway-app]

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

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 27, 2026 at 3:32 am
ladle	❌ Build Failed (View Logs)	Web	Feb 27, 2026 at 3:30 am
frontend-inspector	😴 Sleeping (View Logs)	Web	Feb 27, 2026 at 3:30 am
frontend-cloud	😴 Sleeping (View Logs)	Web	Feb 27, 2026 at 3:29 am
mcp-hub	✅ Success (View Logs)	Web	Feb 27, 2026 at 3:19 am

[MasterPtato]

• chore: bump rivetkit protocol version #4329
• fix(udb): add txn tagging #4328
• fix(api): make actor destroy wait for ack #4327
• chore: flatten runtime config #4326
• chore: deploy patch #4324 👈 (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: deploy patch

Summary: Small, focused operational patch covering four areas: a workflow builder escape hatch, an epoxy purge cache fix using that escape hatch, pegboard serverless receiver tag additions, and log level adjustments.

---

Issues

1. Method name inconsistency on WorkflowBuilder

File: engine/packages/gasoline/src/builder/common/workflow.rs

The method bypass_signal_from_workflow_I_KNOW_WHAT_IM_DOING on WorkflowBuilder has "signal" in the name, but it's actually bypassing the restriction on dispatching workflows from within an operation. The SignalBuilder version makes sense, but the WorkflowBuilder version is misleadingly named. Consider a name like bypass_dispatch_from_workflow_I_KNOW_WHAT_IM_DOING for the WorkflowBuilder variant.

2. Structured logging violation on touched line

File: engine/packages/guard-core/src/server.rs (line 115)

The changed line uses positional format arguments instead of tracing fields:

// Current (violates CLAUDE.md convention)
tracing::warn!("{} connection error: {}", port_type_str, err);

// Should be
tracing::warn!(%err, port_type = %port_type_str, "connection error");

Since this line was actively changed (from error! to warn!), this was an opportunity to fix the structured logging pattern as well. CLAUDE.md explicitly requires: "Do not format parameters into the main message, instead use tracing's structured logging."

3. Pre-existing glob import (not introduced by PR, but worth noting)

File: engine/packages/epoxy/src/ops/propose.rs (line 1)

use anyhow::*;

CLAUDE.md states: "Do not glob import (::*) from anyhow." This wasn't introduced by this PR but the file was modified here.

---

Minor Notes

• The bypass escape hatch design is reasonable for a known temporary workaround. The deliberately alarming name, the // TODO: Get rid of this (RVT-5281) comment with a ticket reference, and the inline documentation of why it's a "bad implementation" are all good practices.
• No tests for the bypass method. The PR checklist acknowledges this. A test verifying the bypass only clears CannotDispatchFromOpInWorkflow (and not other error variants) would prevent regressions when the bypass logic is eventually replaced.
• Log level adjustments are well-reasoned. The NATS Closed → info downgrade with the "Engine is shutting down, not an error" comment is clear. The guard connection error error → warn downgrade is appropriate for edge-level connection drops.
• Tag additions in pegboard receiver correctly enable workflow lookup and deduplication by namespace_id and runner_name.

---

Summary

The only actionable item before merge is the structured logging violation on the touched line in guard-core/src/server.rs:115. The method naming inconsistency is minor but worth addressing since the escape hatch is meant to be temporary (so the name won't need to live forever). Everything else is either pre-existing or acceptable.

[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
• example-elysia
• 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-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• 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
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/virtual-websocket

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

@rivetkit/cloudflare-workers

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/sqlite-vfs

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

@rivetkit/traces

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

@rivetkit/workflow-engine

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

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: 7f4c3d9

[MasterPtato]

This change is part of the following stack:

• chore: deploy patch #4324 ◀
  • chore: flatten runtime config #4326
    • fix(api): make actor destroy wait for ack #4327
      • fix(udb): add txn tagging #4328
        • chore: bump rivetkit protocol version #4329

_{Change managed by git-spice.}