rivet-dev/actors
52.5
Weak · 14 November 2026
397.2k
lines of production code
Rust
with TypeScript
5
measurements over time
What this system is
Features
Add Hello World example demonstrating real-time actor state
A new Hello World example has been added to the examples directory, providing a minimal, runnable demonstration of RivetKit. This example showcases core capabilities including persistent actor state management, real-time synchronization of a counter across multiple clients via events, and integration with React using the \@rivetkit/react\ hooks. It includes the necessary frontend components, server setup, and configuration files to run the demo locally.
examples/hello-world · high confidence
Add Python bindings for async and sync Rivetkit clients
This change introduces the Python client library for Rivetkit, exposing both asynchronous and synchronous APIs. Users can now instantiate \AsyncClient\ and \AsyncSimpleClient\ for non-blocking operations or \Client\ and \SimpleClient\ for synchronous usage. The bindings support connecting via WebSocket or SSE transports and JSON or CBOR encodings. Key capabilities include actor management (get, create, get\_with\_id), invoking actor actions, and handling events through subscription and reception mechanisms.
rivetkit-python/client · high confidence
Add RivetKit DevTools browser extension
A new \devtools\ package has been added to the RivetKit monorepo, providing a browser-based developer tool. It injects a draggable, floating UI button into the page that opens the RivetKit Inspector in a new tab, automatically passing the client's endpoint, token, namespace, and pool name as URL parameters. The package includes the React components, hooks for positioning and dragging, and build configuration to bundle the UI as an IIFE script. Also in this area: 2 commits (0 fixes) modifying (repo-wide); 1 commit (0 fixes) modifying (repo-wide); Removal of the built-in agentOS actor from RivetKit; Fix browser client request body handling by sending bytes instead of streams; Fixes for UserError serialization and workflow logging context.
rivetkit-typescript/packages/rivetkit · low confidence · unverified
Add SQLite + Drizzle ORM example project
Introduces a new example project demonstrating how to integrate Drizzle ORM with SQLite in Rivet Actors. The example includes a pre-configured Drizzle setup with a \users\_table\ schema, automatic migration files, and a \.env.sample\ for local database configuration, providing a reference for type-safe database operations within actors.
examples/sqlite-drizzle · high confidence
Add experimental AI agent example using durable streams
This location introduces a new example project demonstrating an AI agent that communicates via durable streams for reliable message delivery. The example includes a React frontend chat UI, a backend actor that consumes prompts and streams Anthropic (Claude) responses, and an in-memory durable streams test server for development. It requires an Anthropic API key and illustrates the architecture where prompts and responses flow through separate durable streams per conversation.
examples/experimental-durable-streams-ai-agent · high confidence
Add frontend UI for the experimental durable streams AI agent example
The frontend directory for the experimental durable streams AI agent example now includes the React application files (App.tsx, App.css, main.tsx). This adds a chat-based user interface that connects to the AI agent actor via RivetKit, allowing users to view conversation history, send messages, and see streaming responses in real-time.
examples/experimental-durable-streams-ai-agent/frontend · high confidence
Add hello-world container image for Rivet Compute
A new hello-world container image is now available for Rivet Compute, allowing users to verify their setup with a simple Node.js application. The image serves a branded HTML page via HTTP on port 8080, providing a quick way to confirm that container deployment and networking are functioning correctly before building custom applications. Also in this area: Updated documentation links to reflect new rivet.dev site structure.
docker/compute-hello-world · high confidence
Add opt-out telemetry with simplified Sentry configuration
The telemetry package now initializes Sentry error reporting only when explicitly enabled in the configuration (defaulting to opt-out). It captures structured metadata tags for the database, pubsub, and cache drivers to aid in debugging, while ensuring that sensitive configuration details like server URLs or credentials are never sent to Sentry.
engine/packages/telemetry · high confidence
Add raw WebSocket cursor collaboration example
The \examples/cursors-raw-websocket/frontend\ directory now contains a new React application (\App.tsx\ and \main.tsx\) that demonstrates real-time cursor collaboration using raw WebSockets. The app connects to a RivetKit server to manage a shared room, handling cursor movement, removal, and synchronized text labels via direct WebSocket messages, while managing local state for user identity, connection status, and canvas scaling.
examples/cursors-raw-websocket/frontend · high confidence
Add real-time collaborative cursors example
The \examples/cursors\ directory now includes a complete demo application showcasing real-time cursor tracking and collaborative canvas features. This example demonstrates how to use Rivet Actors to broadcast cursor positions to all connected users via WebSockets, manage persistent canvas state (such as text labels) across sessions, and organize collaboration into isolated rooms. It serves as a reference implementation for building multi-user interactive experiences using the platform's actor events and state management capabilities.
examples/cursors · high confidence
Added raw WebSocket chat frontend example
The raw-websocket-handler example now includes a React frontend (App.tsx and main.tsx) that demonstrates connecting to a WebSocket actor using the RivetKit SDK. Users can see a working chat interface that establishes a direct WebSocket connection, displays real-time messages, and allows sending text, illustrating how to handle raw WebSocket streams in a browser environment.
examples/raw-websocket-handler/frontend · high confidence
Auto-generated engine configuration and API documentation schemas
The engine now automatically generates and publishes its configuration schema and public API documentation during the build process. A new build script creates \config-schema.json\ in the engine artifacts directory, reflecting the requirement that authentication must be configured for a running engine. Additionally, an OpenAPI specification (\openapi.json\) for the public API router is generated and written to the same artifacts directory, ensuring documentation stays synchronized with the code.
engine/packages/config-schema-gen · high confidence
Automated Rust and TypeScript SDK generation for Envoy Protocol
The build process now automatically generates Rust and TypeScript SDKs from local schema files during compilation. This ensures the Rust crate includes the correct protocol version constant and that the TypeScript SDK is built with the correct imports (replacing internal @bare-ts/lib references with @rivetkit/bare-ts) and a custom assertion function, making the generated code ready for distribution and use without manual intervention.
engine/sdks/rust/envoy-protocol · high confidence
Epoxy v2 proposal and backfill operations introduced
The Epoxy engine now exposes v2 proposal logic and a background backfill workflow. The new \ops/propose\ module handles single-command proposals (Set and Check-and-Set) with explicit consensus failure reasons (prepare/accept phase failures, stale ballots, value mismatches) and optional replica scoping. A new \ops/read\_cluster\_config\ operation retrieves the current cluster configuration from the underlying database. Additionally, the \workflows/backfill\ module implements \epoxy\_backfill\_v2\, which migrates legacy committed values and changelog data to the v2 format in chunks, ensuring new learners can access the updated changelog while old data remains readable via dual-read fallback until migration completes. Also in this area: 1 commit (0 fixes) modifying (repo-wide); Epoxy KV read operations now support multiple consistency modes; Epoxy consensus engine core implementation.
engine/packages/epoxy · low confidence · unverified
Initial implementation of the Guard service with routing, metrics, and TLS support
The Guard service has been introduced as a new component within the engine to handle request routing, security, and observability. It provides structured error handling for routing failures (such as missing headers, invalid parameters, or timeouts) and exposes detailed Prometheus metrics for monitoring route dispatch durations, gateway selections, and authorization checks. The service initializes shared state for multiple pegboard gateway versions and integrates with JWT authentication caches, while also including a placeholder for TLS certificate resolution to support future HTTPS configurations. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/guard · low confidence · unverified
Initial release of the Envoy Protocol TypeScript SDK
This change introduces the \envoy-protocol\ TypeScript SDK, providing generated serialization and deserialization functions for the Envoy protocol's binary format. The SDK exposes types for identifiers (Id, GatewayId, RequestId), key-value store operations (KvKey, KvValue, KvMetadata), and various query types (KvListAllQuery, KvListRangeQuery, KvListPrefixQuery). It also includes support for HTTP stream abort reasons and is configured to build for both CommonJS and ESM targets using tsup. A golden test is included to verify the correctness of the HTTP abort message encoding against expected binary bytes.
engine/sdks/typescript/envoy-protocol · high confidence
Inspector UI bundle now ships embedded in the rivetkit-core crate
The inspector UI and tab assets are now bundled directly into the published rivetkit-core crate, ensuring the inspector UI is served from embedded memory rather than degrading to a 404. A new build.rs stages the frontend dist into the crate during packaging, and a release verification script confirms the assets are included in the archive and served correctly at runtime.
rivetkit-rust/packages/rivetkit-core · high confidence
Introduce @rivetkit/rivetkit-wasm package for browser-based actor runtime
This change adds a new npm package that bundles the Rivetkit core engine into a WebAssembly module, enabling actors to run directly in the browser or WebWorker environments. The package includes a Rust source implementation (src/lib.rs) that bridges core actor lifecycle, HTTP serving, and SQLite storage to JavaScript via wasm-bindgen, along with build scripts to compile the WASM artifact and validation checks to ensure the published package contains all necessary files. Users can now import and initialize the Rivetkit runtime in client-side applications without requiring a separate native engine process.
rivetkit-typescript/packages/rivetkit-wasm · high confidence
Introduce React integration for RivetKit actors
This change adds the \@rivetkit/react\ package, providing React-specific hooks to integrate with RivetKit actors. It introduces \createRivetKit\ and \createRivetKitWithClient\ to initialize the client, and exposes a \useActor\ hook that manages actor connection state (including \isConnected\, \isConnecting\, and \connStatus\) and provides a \useEvent\ method for subscribing to actor events with full type safety. The package includes configuration files (\tsconfig.json\, \tsup.config.ts\, \turbo.json\) to support building and bundling the React bindings.
rivetkit-typescript/packages/react · high confidence
Introduce Rivet CLI with compute pool, token, and logging capabilities
The CLI now supports managing Rivet Compute infrastructure directly from the command line. Users can create and manage namespace-scoped tokens via the new \token\ command, view and filter logs for compute instances with the \logs\ command, and manage compute pools (including creation, deletion, and configuration) via the \pool\ command. Deployment commands now accept resource flags such as \--cpu\, \--memory\, \--min-scale\, \--max-scale\, and \--instance-request-concurrency\ to configure managed pool resources, along with runner configuration flags like \--max-concurrent-actors\. Authentication is handled via a new credential file at \\~/.rivet/credentials\ or the \RIVET\_CLOUD\_TOKEN\ environment variable, and the CLI includes a \setup-ci\ command to install a GitHub Actions workflow for automated deployments.
engine/packages/cli/src · high confidence
Introduce RivetError derive macro for structured error handling
Adds the \engine/packages/error-macros\ crate, which provides the \RivetError\ procedural macro. This allows developers to derive error types that automatically generate structured error schemas, supporting both named and unnamed struct fields with optional formatted descriptions. The macro integrates with the \rivet\_error\ and \anyhow\ crates to produce standardized error objects with metadata.
engine/packages/error-macros · high confidence
Introduce WebSocket hibernation and keepalive mechanisms in the Pegboard Gateway
The Pegboard Gateway now supports WebSocket hibernation, allowing idle WebSocket connections to be suspended and resumed without dropping the underlying request state. This change introduces dedicated tasks to manage the lifecycle of hibernating connections: a keepalive task periodically updates the request's status in the database to prevent garbage collection, a ping task sends regular pings to maintain the tunnel connection, and a metrics task tracks ingress and egress byte counts for monitoring. The shared state logic has been updated to handle hibernation states, manage pending message queues, and enforce timeouts, ensuring that in-flight requests remain valid while the WebSocket is hibernated. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/pegboard-gateway · low confidence · unverified
Introduce base framework package with actor management and TypeScript configuration
This change introduces the \framework-base\ package, establishing the foundational infrastructure for actor management in RivetKit. It adds the \ActorOptions\ interface, which now supports a \noCreate\ option to retrieve existing actors without creating new ones, and defines the \createRivetKit\ function to initialize the actor store and cache. The package also includes standard TypeScript build configuration (\tsconfig.json\, \tsconfig.build.json\) and bundler setup (\tsup.config.ts\) to support the framework's module resolution and compilation.
rivetkit-typescript/packages/framework-base · high confidence
Introduce guard-core library for request proxying and TLS management
The guard-core library has been added to the engine, providing the core logic for the Guard service. It includes a custom TLS certificate resolver for SNI-based HTTPS support, a comprehensive error type system for structured error reporting, and a proxy service that handles HTTP and WebSocket routing, caching, and admission controls (rate limiting and in-flight request limits). The library also exposes detailed metrics for gateway requests, TCP connections, and WebSocket operations, along with utilities for request context management and response body streaming. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/guard-core · low confidence · unverified
Introduce initial Rust client for RivetKit actors
Adds the \rivetkit-client\ Rust package, providing a new way for Rust applications to connect to and interact with RivetKit actors. The client supports WebSocket transport for actor connections and offers multiple encoding formats (JSON, CBOR, and Bare). It exposes APIs for getting, creating, and getting-or-creating actors, as well as sending actions, queueing messages, and subscribing to actor events. The implementation includes a remote manager for gateway communication, backoff logic for reconnection, and comprehensive protocol handling for both HTTP and WebSocket interactions.
rivetkit-rust/packages/client · high confidence
Introduce platform-specific binary resolution for the Rivet engine CLI
The \@rivetkit/engine-cli\ package now provides a JavaScript entry point that automatically resolves the correct \rivet-engine\ binary for the current host (Linux x64/arm64, macOS Intel/Apple Silicon, and Windows x64 on release builds). It supports overriding the binary path via the \RIVET\_ENGINE\_BINARY\ environment variable and falls back to a local binary for development, ensuring the engine binary is available across supported platforms without manual configuration.
rivetkit-typescript/packages/engine-cli · high confidence
Introduce structured error handling and registry web handler in @rivetkit/effect
The \@rivetkit/effect\ package now provides a comprehensive, schema-driven error classification system via \RivetError\, replacing generic failures with granular reason classes (e.g., \ActorNotFound\, \GuardServiceUnavailable\, \ActionErrorDecodeFailed\) that expose normalized accessors like \isRetryable\ and \retryAfter\. This structured approach ensures that action error metadata is correctly decoded and surfaced to users. Additionally, the package introduces a \Registry\ module with a \toWebHandler\ adapter, allowing registered actors to be served as standard Fetch-compatible HTTP handlers with configurable serverless routing options like \basePath\ and \maxStartPayloadBytes\. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
rivetkit-typescript/packages/effect · low confidence · unverified
Introduces native and WASM WebSocket transport implementations for the Envoy client
The \envoy-client\ SDK now supports connecting to the Envoy control plane via WebSocket on both native Rust and WebAssembly targets. This change adds \connection/mod.rs\, \connection/native.rs\, and \connection/wasm.rs\ to handle connection lifecycle, including session management, reconnection with exponential backoff, and streaming HTTP bodies over the WebSocket tunnel. The implementation enforces mutual exclusivity between \native-transport\ and \wasm-transport\ features and includes byte-budgeting for HTTP messages to prevent unbounded memory usage.
engine/sdks/rust/envoy-client/src/connection · high confidence
Introducing the durable TypeScript workflow engine
The \@rivetkit/workflow-engine\ package is now available, providing a durable execution system for TypeScript that enables long-running, fault-tolerant workflows. Workflows are written as standard async functions and automatically persist their history to an \EngineDriver\, allowing them to survive process crashes, restarts, and deployments by replaying from the last known state. The engine supports complex control flow including durable loops with state checkpoints, parallel execution via \join\ and \race\, and external event handling through queue waits. It also includes built-in fault tolerance with automatic step retries, rollback handlers for undoing completed steps on failure, and helpers like \tryStep\ and \try\ to manage terminal errors gracefully. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
rivetkit-typescript/packages/workflow-engine · low confidence · unverified
Introduction of the service-manager package for runtime service orchestration
The new \engine/packages/service-manager\ package provides the core runtime logic for managing and executing background services. It defines a \Service\ struct and \ServiceKind\ enum to categorize workloads (such as \ApiPublic\, \Standalone\, \Oneshot\, \Cron\, and \Core\) and dictates their lifecycle behavior, including automatic restarts for long-running services and scheduled execution for cron jobs. The \start\ function orchestrates these services, integrating a metrics server, handling SIGTERM signals for graceful shutdown, and managing task concurrency via Tokio.
engine/packages/service-manager · high confidence
Kitchen-sink example expanded with comprehensive actor lifecycle and integration demos
The kitchen-sink example has been significantly expanded to demonstrate a wide range of RivetKit actor capabilities. New examples cover action inputs and timeouts, synchronous and asynchronous action patterns, and detailed error handling with UserError. It now includes actors for managing WebSocket connections with per-connection state, rejecting connections, and accessing raw HTTP request properties. The example also features raw HTTP routing using Hono, a WebSocket chat room, and serverless WebSocket smoke tests. Inter-actor communication is demonstrated through an inventory and checkout workflow. Lifecycle management is thoroughly covered with examples for hibernation, sleep/wake cycles, scheduled tasks, run handlers with queue consumption, and actor destruction observers. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
(repo-wide) · low confidence · unverified
New AI Agent example with queue-driven streaming
The \examples/ai-agent\ directory now includes a complete example demonstrating a queue-driven Rivet Actor AI agent pattern. It features a React frontend (using \@rivetkit/react\) that connects to a backend where an \AgentManager\ actor coordinates multiple agent actors. Each agent consumes messages from a queue, streams responses via the Vercel AI SDK (using OpenAI), and broadcasts live status and message updates to the UI. The example includes the necessary configuration files (\tsconfig.json\, \vite.config.ts\, \turbo.json\) and a \.gitignore\ to support local development.
examples/ai-agent · high confidence
New AI agent example using the Effect SDK
The \examples/ai-agent-effect\ directory now contains a complete example of an AI chat agent built with the Effect SDK. It defines an \Agent\ actor with \SendMessage\ and \GetHistory\ actions, persisting conversation turns in state. The implementation uses dependency injection to swap the underlying LLM provider, defaulting to OpenAI via \OpenAiModelLayer\, and includes client and server wiring examples with telemetry support. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
examples/ai-agent-effect · low confidence · unverified
New API builder library for Axum-based services
The \engine/packages/api-builder\ package introduces a new Rust library that simplifies building HTTP APIs with Axum. It provides a standardized request context (\ApiCtx\) for dependency injection, a structured error handling system that maps internal errors to specific HTTP status codes and JSON responses, and custom extractors for JSON, query, path, and extension data. The library includes a router factory that automatically configures CORS, request logging, metrics (pending requests, total count, duration, errors), and OpenTelemetry tracing, along with helper macros for defining route handlers for all standard HTTP methods.
engine/packages/api-builder · high confidence
New Docker base images for engine and rivetkit builds
Added a suite of Docker base images in docker/builder-base to standardize and accelerate cross-platform builds. The engine-builder image provides a Linux environment with Rust 1.91.1, Node.js 22, and FoundationDB 7.3.68 for engine container builds. Runtime images (full and slim) supply the FoundationDB client library for Linux deployments. Platform-specific images (linux-gnu, linux-musl, osxcross, windows-mingw) pre-configure the necessary toolchains (Clang 14, MinGW, osxcross), Rust targets, Node.js 22, and sccache to support native addon compilation for Linux, macOS, and Windows.
docker/builder-base · high confidence
New JWT counter example demonstrating scoped token issuance and renewal
Added a new example application in \examples/jwt-counter\ that demonstrates a minimal JWT authentication flow. The example includes a React frontend and a Hono-based server that issues short-lived (30-second), namespace-scoped JWT tokens for a specific counter actor. It showcases automatic token renewal via RivetKit's \getToken\ callback, actor isolation (ensuring tokens cannot access other actors), and handles token expiry and invalidation without replaying failed actions. A smoke test verifies the end-to-end behavior including token issuance, CLI usage, scope enforcement, and renewal mechanics.
examples/jwt-counter · high confidence
New Kitchen Sink frontend application for interactive demos
The examples/kitchen-sink/frontend directory now contains a complete React-based frontend application (App.tsx, main.tsx, page-data.ts) that serves as an interactive demo hub. It integrates with the RivetKit client to allow users to interact with various actor types (actions, state, events, workflows, SQLite, AI) via a sidebar navigation, displaying Mermaid diagrams and code snippets for each feature.
examples/kitchen-sink/frontend · high confidence
New React integration example with Vite and RivetKit
A new React example has been added to the examples directory, demonstrating how to build a frontend with Vite that connects to Rivet Actors. The example includes a React application using the \@rivetkit/react\ library for type-safe actor communication and real-time event subscriptions, alongside a backend setup that registers actors and starts the server using \registry.start()\. It serves as a reference for integrating React UIs with Rivet's actor model.
examples/react · high confidence
New Rivet CLI commands for deployment, local development, and pool management
The CLI now includes a suite of new commands to manage the full lifecycle of Rivet applications. The \deploy\ command allows users to build and push Docker images to managed compute pools, with new flags to configure compute resources (CPU, memory, scaling limits) and a \--reuse-image\ option to update resources without rebuilding. Local development is streamlined with the \dev\ command, which supports providers like Supabase and Cloudflare, automatically injecting the engine endpoint and handling handler registration. Users can now inspect logs with the \logs\ command (supporting live tailing and history filtering) and manage compute pools directly via \pool list\ and \pool delete\. Additionally, the \token\ command enables the creation of namespace-scoped tokens (secret, public, or connection), and \setup\_ci\ generates a GitHub Actions workflow for automated deployments. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/cli/src/commands · low confidence · unverified
New SQLite Raw example with benchmarking and registry startup
The \examples/sqlite-raw\ directory now provides a complete demonstration of using the raw SQLite driver (\@rivetkit/db/raw\) within RivetKit actors. This example includes a \todoList\ actor that performs CRUD operations via raw SQL migrations on wake, alongside a \benchInsertPayload\ action designed to measure performance against native SQLite. The entry point (\src/index.ts\) now explicitly calls \registry.start()\, and the example is supported by a client script for interactive testing and a benchmarking script (\bench-large-insert.ts\) that compares Actor DB latency against local disk SQLite.
examples/sqlite-raw · high confidence
New Scheduling example demonstrating time-based task execution
The examples/scheduling directory now includes a complete demo application that illustrates how to schedule tasks and execute code at specific times or intervals using Rivet Actors. This example showcases key scheduling capabilities, including scheduling actor actions to run after a delay with \schedule.after()\, scheduling at specific timestamps with \schedule.at()\, and persisting these schedules so they survive actor restarts. It also demonstrates canceling pending reminders and broadcasting events upon completion, providing a practical reference for implementing time-based workflows in Rivet.
examples/scheduling · high confidence
New TypeScript API SDK for Node and Browser environments
This change introduces the \api-full\ TypeScript SDK, providing a client library to interact with the Rivet engine API. The SDK includes a \RivetClient\ with resource-specific sub-clients for managing actors, auth tokens, datacenters, envoys, health, metadata, namespaces, and runners. It supports both Node.js (via CommonJS and ESM) and browser environments, generated from the API definition using Fern, and includes a build script to bundle the code for these different targets. Also in this area: 2 commits (0 fixes) modifying (repo-wide).
engine/sdks/typescript/api-full · medium confidence · unverified
New TypeScript API SDK for Node and Browser environments
This change introduces the \api-full\ TypeScript SDK, providing a client library to interact with the Rivet engine API. The SDK includes a \RivetClient\ with resource-specific sub-clients for managing actors, auth tokens, datacenters, envoys, health, metadata, namespaces, and runners. It supports both Node.js (via CommonJS and ESM) and browser environments, generated from the API definition using Fern, and includes a build script to bundle the code for these different targets. Also in this area: Initial release of the Envoy Protocol TypeScript SDK.
engine/sdks/typescript · high confidence
New VirtualWebSocket library for abstracting WebSocket connections
A new shared TypeScript library has been added at shared/typescript/virtual-websocket, introducing a VirtualWebSocket class that implements a UniversalWebSocket interface. This allows developers to create linked WebSocket pairs and delegate send/close operations to callbacks, providing a standardized way to handle WebSocket-like connections without relying on the native browser API directly. The library includes specific event interfaces (RivetEvent, RivetMessageEvent, RivetCloseEvent) with experimental support for gateway and request IDs, and is configured for both ESM and CJS output formats.
shared/typescript/virtual-websocket · high confidence
New api-peer service exposes actor, runner, and depot inspection APIs
A new api-peer service has been introduced to handle specific API endpoints, replacing or supplementing previous routing. It provides a comprehensive set of actor management operations including creation, deletion, get-or-create (with duplicate key handling), listing, and key-value retrieval, as well as lifecycle controls like sleep and reschedule. The service also exposes endpoints for listing and managing namespaces, runners, runner configs, and envoys. Additionally, it offers a detailed depot inspection API for debugging and inspecting database buckets, branches, and raw keys, along with internal endpoints for cache purging, epoxy coordinator state management, and profiling configuration. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/api-peer · low confidence · unverified
New chat-room example with real-time messaging and actor state
The chat-room example now demonstrates real-time messaging using Rivet actors, featuring persistent chat history stored in SQLite and event-driven updates to connected clients. The frontend allows users to join specific rooms by name and send messages, while the backend actor manages message persistence and broadcasts new messages to all participants in the room. This example also includes a comprehensive test suite verifying message ordering, multi-user support, and history retrieval.
examples/chat-room · high confidence
New chat-room-effect example demonstrating typed actor interactions
Added a new example under \examples/chat-room-effect\ that showcases the \@rivetkit/effect\ SDK. It implements a \ChatRoom\ actor with schema-validated actions (Initialize, Join, Leave, SendMessage, GetHistory, Archive) and a \Moderator\ actor for content filtering. The example includes both a raw HTTP client (\client-raw.ts\) and an Effect-native client (\client.ts\) to demonstrate how domain errors like \MemberNotNotInRoomError\ and \BannedWordsError\ are handled, along with server-side wiring (\main.ts\) and telemetry layers. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
examples/chat-room-effect · low confidence · unverified
New collaborative cursor and text annotation example
Added a new frontend example in \examples/cursors/frontend\ that demonstrates real-time collaborative editing. The application uses \@rivetkit/react\ to connect to a server, allowing multiple users to see each other's cursors on a shared virtual canvas and to add, edit, and remove synchronized text labels. It handles room state synchronization, cursor movement events, and text updates via a React-based UI with scaling support.
examples/cursors/frontend · high confidence
New developer tooling and API helper scripts
This change introduces a suite of new scripts to aid development and debugging. In scripts/api, it adds interactive CLI helpers for managing actors and runner configurations (create, list, upsert, delete) and for pinging actors via the gateway. In scripts/cargo, it adds a script to update the Rust workspace Cargo.toml, a check to ensure rivetkit-core builds cleanly for WebAssembly without native dependencies, and utilities to fix linting issues and kill orphaned test processes. In scripts/ci, it adds a guard to prevent native packages from leaking into the Supabase edge adapter bundle. Finally, in scripts/debug, it adds several decoders for internal binary formats (Epoxy, runner config, FDB tuples), a Mermaid gantt debugger, a log-to-gantt converter, an endian converter, and a local web server for viewing git diffs. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
scripts · low confidence · unverified
New example demonstrating real-time collaborative cursors with raw WebSockets
A new example project has been added at examples/cursors-raw-websocket that demonstrates real-time cursor tracking and collaborative canvas editing using raw WebSocket handlers instead of higher-level abstractions. The example includes a frontend interface for displaying and moving cursors, and a backend actor implementation that manages WebSocket connections, broadcasts cursor positions to all connected users, and persists text labels in actor state across sessions.
examples/cursors-raw-websocket · high confidence
New example demonstrating scoped JWT authentication with Better Auth
The \examples/jwt-better-auth\ directory now provides a complete React-based example showing how to integrate Better Auth for user sessions with RivetKit's scoped JWT issuance. The example features a frontend that handles signup and login via Better Auth, while the backend verifies the session to issue short-lived, actor-scoped tokens (defaulting to \read\ gateway access) for the user's specific actor. It includes a smoke test that validates per-user actor isolation, automatic token renewal upon expiry, and the rejection of actions after logout.
examples/jwt-better-auth · high confidence
New examples for actor actions and agentOS
Added the \actor-actions\ example, which demonstrates type-safe RPC-style communication between actors and clients using RivetKit actions and state management, and the \agent-os\ example, which shows how to run coding agents inside isolated VMs with filesystem, process, and network control. Also added an \agent-os-e2e\ smoke test that exercises these agentOS capabilities end-to-end. Also in this area: 1 commit (0 fixes) modifying (repo-wide); Add documentation guides for real-time, cron, and per-tenant database patterns.
(repo-wide) · low confidence · unverified
New examples for actor actions and custom serverless deployment
Added two new example projects to demonstrate core platform capabilities. The \actor-actions\ example shows how to define and call type-safe actions on Rivet Actors for RPC-style communication, including creating actors with input parameters, managing state, and handling cross-actor interactions (e.g., a company actor creating employee actors). The \custom-serverless\ example demonstrates deploying actors to custom serverless infrastructure with automatic engine configuration, featuring a simple counter actor with state and event broadcasting. Both examples include full TypeScript support, frontend UIs (where applicable), and comprehensive test suites.
examples/actor-actions · high confidence
New geo-distributed database example demonstrating edge-local session state
Added a new example in \examples/geo-distributed-database\ that demonstrates storing user session state in edge-local Rivet Actors to keep preferences and activity close to users. The example includes a React frontend (\frontend/App.tsx\) that visualizes data locality on a world map and measures action latency, alongside backend logic (\src/index.ts\) that initializes region-specific actors using \createInRegion\ and persists session data such as theme, language, and recent activity.
examples/geo-distributed-database · high confidence
New hello-world-effect example demonstrates Rivet Effect SDK usage
This change introduces a new \hello-world-effect\ example that showcases the \@rivetkit/effect\ SDK for building Rivet Actors. It provides a complete, runnable reference implementation including a typed \Counter\ actor definition with schema-validated actions (\Increment\, \GetCount\) and custom error handling (\NegativeAmountError\). The example demonstrates server-side actor implementation using Effect layers, client-side interaction via the typed client API, and integration with observability tools like Pino logging and OpenTelemetry tracing. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
examples/hello-world-effect · low confidence · unverified
New multiplayer game pattern examples added
The multiplayer-game-patterns example now includes reference implementations for several game genres, including Arena, Battle Royale, Idle, IO-style, Open World, Party, Physics 2D/3D, Ranked, and Turn-Based modes. Each pattern provides a complete backend structure with dedicated matchmaker actors for player matching and lobby management, along with match actors that handle game state, tick loops, and event broadcasting. The examples demonstrate various matchmaking strategies such as queue-based filling, two-phase reservation with pending player expiration, and private party creation with join tickets, alongside game logic patterns like zone shrinking, resource production, and chunk-based world partitioning. Also in this area: 1 commit (0 fixes) modifying (repo-wide); Add documentation guides for real-time, cron, and per-tenant database patterns.
examples/multiplayer-game-patterns/src/actors · low confidence · unverified
New per-tenant database example with isolated actor state
Added a new example project in \examples/per-tenant-database\ that demonstrates how to isolate data per company using Rivet Actors. The example includes a React frontend (\frontend/App.tsx\) that allows users to switch between companies, with each company mapped to a distinct \CompanyDatabase\ actor instance. The backend (\src/index.ts\) defines the actor schema, actions (like \addEmployee\, \listProjects\), and events, ensuring that state is strictly isolated by the actor key. The entry also includes configuration files for Vite, TypeScript, and Vitest, along with tests verifying that data remains separate across different company keys.
examples/per-tenant-database · high confidence
New publish workflow tooling for CI and local releases
The \scripts/publish\ directory now contains a complete, structured publish system. The CI entrypoint (\bin.ts\) orchestrates releases via subcommands, resolving context once and passing it to downstream steps. It supports selective preview publishes via a \targets\ input (rivetkit, container-runner, engine, cli) and allows custom preview names. The system handles version bumping for both npm (\package.json\) and Rust (\Cargo.toml\) workspaces, including injecting optional dependencies for meta-packages at publish time. It manages npm publishing with parallelism, retries, and idempotency, and handles Docker multi-arch manifest creation and retagging. It also manages Git tagging, GitHub release creation, and uploading assets to R2. A local \cut-release\ script is provided for manual release cuts, which updates source files, runs checks, and triggers the CI workflow. Also in this area: 1 commit (0 fixes) modifying (repo-wide); Removal of agentOS example applications; Removed @rivet-dev/pi and @rivet-dev/sandbox-adapter from publish configuration; Fix independent package versioning and release filtering in publish script; Support for independent versioning and preview builds in the publish script.
scripts/publish · low confidence · unverified
New standalone metrics server with OpenTelemetry support
The metrics-server package has been restructured into a standalone service that exposes Prometheus metrics via HTTP and integrates OpenTelemetry tracing. It now supports dynamic trace sampling ratios that can be updated at runtime, initializes OpenTelemetry providers based on environment variables, and provides a dedicated HTTP endpoint for scraping metrics.
engine/packages/metrics-server · high confidence
New tracing utilities for custom future instrumentation and metrics
The \tracing-utils\ package now includes a new \lib.rs\ module providing a \select\_all\_or\_wait\ helper for non-panicking future selection and a \CustomInstrumentExt\ trait. This trait allows futures to be instrumented with custom spans that automatically record duration metrics (exposed as Prometheus histograms) upon completion, enhancing observability for asynchronous operations.
engine/packages/tracing-utils · high confidence
New utility primitives for throttling, serialization, and async operations
The \engine/packages/util\ crate now includes a suite of new capabilities: a \RateLimiter\ supporting both Fixed Window and Leaky Bucket algorithms with blocking and non-blocking acquisition, an \AsyncCounter\ for tracking concurrent operations with zero-state notifications, and a \SimpleValue\ type for serializing/deserializing flat JSON structures. It also introduces observability macros (\observe!\, \json\_to\_vec!\, etc.) that automatically record duration and size metrics for code blocks and serialization calls, alongside helper modules for duration formatting, input validation, and safe string slicing.
engine/packages/util · high confidence
Rivet engine CLI and service initialization structure
The engine package now exposes a structured CLI entry point (\main.rs\) and a library interface (\lib.rs\) that define the available subcommands (Start, Database, Workflow, Config, Auth, Tracing, Profile, Epoxy, Depot, Udb) and their execution flow. The \run\_config.rs\ module registers the core services (api\_peer, guard, workflow\_worker, pegboard\_outbound, bootstrap, dynamic\_config, version\_management, epoxy\_protocol\_version, cache\_purge, profiling) with their respective service kinds and startup logic, establishing the runtime's service topology. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/engine · low confidence · unverified
Rivetkit runtime adapter moves to a native N-API implementation
The \rivetkit-napi\ package now provides a Rust-based native binding (N-API) that replaces the previous TypeScript-only runtime adapter. This change introduces a new build pipeline (using \build.rs\ and \napi-build\) and ships precompiled binaries for multiple platforms (Linux x64/arm64, macOS, Windows, Android). For users, this means the core actor lifecycle, state management, key-value storage, database access, HTTP streaming, and queue operations are now executed in native code, exposing a consistent JavaScript/TypeScript interface via \index.d.ts\ and \index.js\ while improving performance and stability for the Rivetkit actor runtime.
rivetkit-typescript/packages/rivetkit-napi · high confidence
Rust SDK introduces versioned data schemas and migration logic
The Rust SDK now includes a new \data\ crate that provides versioned wrappers for Pegboard and Auth schemas, enabling safe serialization and deserialization across multiple schema versions. This change adds build-time schema processing to generate version constants and implements explicit migration converters for \NamespaceRunnerConfig\ (V1–V6), \AuthJwtKeyRing\ (V1–V3), and \RunnerAllocIdxKey\ (V1–V2), ensuring that existing data can be upgraded to the latest schema version automatically. Also in this area: 2 commits (0 fixes) modifying (repo-wide); 1 commit (0 fixes) modifying (repo-wide).
engine/sdks/rust/data/src · low confidence · unverified
Rust actor framework implementation
The \rivetkit\ package is now implemented in Rust, providing a typed wrapper over \rivetkit-core\ that mirrors the TypeScript API. This introduces a new \Actor\ trait for defining actors, a \Ctx\ context for managing state and client interactions, and typed handling for actions, events, and queues. The framework supports both Envoy and serverless runtime modes, configurable via the \RIVETKIT\_RUNTIME\_MODE\ environment variable, and includes a test harness for in-process end-to-end actor testing.
rivetkit-rust/packages/rivetkit · high confidence
Rust envoy-client SDK introduced with full actor lifecycle and streaming support
The Rust envoy-client SDK is now available in the \engine/sdks/rust/envoy-client\ crate, providing a native implementation for managing actor lifecycles, HTTP streaming, WebSocket tunnels, and key-value/SQLite interactions. This SDK exposes a comprehensive \EnvoyCallbacks\ interface for handling actor start/stop events, fetch requests, and WebSocket connections, while internally managing command deduplication, event persistence, and connection health via ping checks. It supports both standard Rust and WebAssembly targets, includes debug tools like artificial latency injection, and exposes detailed Prometheus metrics for observability.
engine/sdks/rust/envoy-client/src · high confidence
Supabase example adds RivetKit WASM support
The Supabase example in the kitchen-sink directory now supports the RivetKit runtime via WebAssembly. This change introduces a new Supabase Edge Function (\functions/rivetkit\) that initializes the RivetKit engine using a WASM binary, registers specific actors (counter, HTTP, WebSocket, and SQLite testing), and exposes a handler at \/api/rivet\ to process requests. Configuration files (\config.toml\, \.gitignore\, \deno.json\) have been added to support this local development setup, including ignoring the generated WASM file and defining necessary dependencies.
examples/kitchen-sink/supabase · high confidence
Unified cross-platform build Dockerfiles for all target architectures
The build system now uses a set of standardized, unified Dockerfiles to produce release artifacts for every supported platform and architecture. New files have been added for darwin-arm64, darwin-x64, linux-arm64-gnu, linux-arm64-musl, linux-x64-gnu, linux-x64-musl, and windows-x64. Each Dockerfile is configured to build the \rivet-engine\, \rivet-cli\, \rivet-container-runner\, or \rivetkit-napi\ targets using the Rust 1.91.1 toolchain, with platform-specific optimizations such as static linking for musl builds, MinGW cross-compilation for Windows, and osxcross for macOS. All builds leverage sccache via Depot.dev for faster compilation and support embedding the \@rivetkit/engine-frontend\ (inspector UI) when the \BUILD\_FRONTEND\ flag is enabled.
docker/build · high confidence
Removals
Matchmaker worker service removed
The \svc/pkg/mm/worker\ service, which previously handled core matchmaker operations such as lobby creation, finding, cleanup, and player registration/removal, has been deleted. This removes the standalone worker process and its associated logic for managing lobby state and player connections.
svc/pkg/mm/worker · high confidence
Party API service removed
The party API service located at \svc/api/party\ has been completely removed from the codebase. This deletion eliminates the entire module, including the authentication middleware (\auth.rs\), data conversion logic (\convert/\), data fetching routines (\fetch/\), and all HTTP route handlers (\route/\) for party management and matchmaker activity. Consequently, the endpoints previously served by this service are no longer available.
svc/pkg/team/worker · high confidence
Party API service removed
The party API service located at svc/api/party has been deleted. This removal eliminates the HTTP endpoints for party management (such as creating, joining, and managing party members), party activity tracking (including matchmaker lobby joining and finding), and the associated authentication, data fetching, and model conversion logic that supported these features.
svc/api/party, svc/pkg/nomad-log/standalone/follower · high confidence
Removal of Bolt-based secrets retrieval module
The Terraform module located at infra/tf/modules/secrets, which previously retrieved secrets by invoking the 'bolt' CLI tool via the HashiCorp external provider, has been deleted. This change removes the infrastructure capability to fetch secret values using the bolt headless reading mechanism, including the associated inputs for secret keys and optional flags, as well as the outputs exposing those values.
infra/tf/modules/secrets · high confidence
Removal of CDN and User-Dev worker services
The \cdn/worker\ and \user-dev/worker\ services have been removed from the system. This deletion eliminates the \cdn-ns-config-populate\ worker, which previously synchronized CDN namespace configurations to Redis, and the \user-dev-game-update\ worker, which dispatched game update notifications to developer team members. Consequently, automatic CDN config population and developer game-update notifications are no longer processed by these specific worker components.
svc/pkg/cdn/worker, svc/pkg/user-dev/worker, svc/pkg/team-dev/ops/halt, svc/pkg/team-dev/standalone/halt-collect · high confidence
Removal of CDN namespace auth user update and get operations
The \cdn-namespace-auth-user-update\ and \cdn-namespace-get\ operations have been removed from the CDN service. This eliminates the ability to update authentication users for a namespace (including password validation and count limits) and retrieve namespace configuration details such as domains, auth types, and associated auth users via the API.
svc/pkg/cdn/ops/namespace-auth-user-update · high confidence
Removal of Cloudflare Tunnel Terraform module
The \infra/tf/modules/cloudflare\_tunnel\ module has been deleted, removing the infrastructure definition for Cloudflare Tunnels, including the tunnel resource, associated DNS CNAME records, and Cloudflare Access policies (both user-based group access and service-token-based access). This change eliminates the automated provisioning of secure tunnel endpoints and their corresponding access controls previously managed by this module.
_infra/tf/modules/cloudflare\tunnel · high confidence
Removal of Cloudflare custom hostname worker implementation
The worker service for managing Cloudflare custom hostnames has been removed. This change deletes the main entry point and all associated worker modules (create, delete, and status\_set) that previously handled the lifecycle of custom hostnames, including creating hostnames via the Cloudflare API, deleting them, and updating their status in the database.
svc/pkg/cf-custom-hostname/worker · high confidence
Removal of IP info lookup operation
The \ip-info\ operation implementation has been removed from the service. This deletes the logic that previously queried the \ips\ table in the database and fetched data from the external \ipinfo.io\ API to resolve IP addresses to geographic coordinates, effectively eliminating this specific IP information retrieval capability.
svc/pkg/ip/ops/info · high confidence
Removal of KV worker implementation files
The source files for the key-value worker service have been deleted, including the main entry point, the workers module, and the specific write worker logic. This removes the ability to process KV write operations, such as upserting or deleting values in the database, from this component.
svc/pkg/kv/worker · high confidence
Removal of NATS test container and captcha utility function
The \lib/test-images\ crate, which provided a \Nats\ test container implementation for integration testing, has been deleted. Additionally, the \serialize\_topic\_str\ utility function from \svc/pkg/captcha/util\, used for converting topic maps to deterministic strings for database keys, has been removed.
lib/test-images, svc/pkg/captcha/util · high confidence
Removal of NSFW image scoring operation implementation
The implementation for the \nsfw-image-score\ operation has been removed from the codebase. This change eliminates the logic that previously handled NSFW image scoring by sending requests to an internal API endpoint (\http://http.nsfw-api.service.consul:21900/batch-classify\) and emitting analytics events for the results. Users relying on this specific operation will no longer have access to this functionality through this service component.
svc/pkg/nsfw/ops/image-score · high confidence
Removal of Nomad log worker implementation
The \svc/pkg/nomad-log/worker\ component has been completely removed from the codebase. This deletion eliminates the Rust-based workers responsible for writing Nomad logs to ClickHouse (\nomad-log-write\) and exporting them to object storage (\nomad-log-export\). Users relying on this specific worker for log persistence and retrieval will no longer have this functionality available through this service path.
(repo-wide) · high confidence
Removal of build creation and listing operations
The \build-create\ and \build-list-for-game\ operations have been removed from the system. This deletion eliminates the ability to initiate new builds (including image upload preparation and database insertion) and to retrieve the list of builds associated with a specific game.
svc/pkg/build/ops/create · high confidence
Removal of chat message validation operations
The \chat-message-body-validate\ and \chat-message-validate\ operations have been removed from the system. This eliminates the server-side validation logic that previously enforced constraints on chat message bodies (such as length limits and required sender IDs) and validated topic-body compatibility (such as restricting party join requests to specific topic types). Users will no longer receive specific validation errors from these endpoints, as the validation functionality itself has been deleted.
svc/pkg/chat-message/ops/body-validate, svc/pkg/chat-message/ops/validate, svc/pkg/game/ops/namespace-validate, svc/pkg/team/ops/validate, svc/pkg/game/ops/validate, svc/pkg/mm-config/ops/namespace-config-validate · high confidence
Removal of chat thread retrieval operations
The \get-for-topic\ and \list-for-participant\ operations in the chat-thread service have been removed. These operations previously handled fetching chat threads by topic (team, party, or direct) and by participant user ID, including the associated database queries and response mapping logic. This change eliminates the ability to retrieve chat threads via these specific endpoints.
svc/pkg/chat-thread/ops/get-for-topic, svc/pkg/chat-thread/ops/list-for-participant · high confidence
Removal of chat utility key generation functions
The \svc/pkg/chat/util\ package has been removed, eliminating the \key\ module that previously provided functions for generating Redis key names for user thread history, thread tail messages, and typing statuses. This change removes the shared utility logic for constructing these specific cache keys from the chat service's utility layer.
svc/pkg/chat/util · high confidence
Removal of chat worker service and last-read timestamp logic
The chat worker service and its associated code have been removed from the codebase. This includes the deletion of the main entry point, the worker module registration, and the specific implementation for the \chat-last-read-ts-set\ worker, which previously handled updating the \last\_read\_ts\ in the \thread\_user\_settings\ table and publishing subsequent read-update messages. Users will no longer have this specific background processing capability available in this component.
svc/pkg/chat/worker · high confidence
Removal of chat-thread get-for-topic and list-for-participant operations
The \chat-thread-get-for-topic\ and \chat-thread-list-for-participant\ operations have been removed from the service. These operations previously handled retrieving chat threads by topic (team, party, or direct) and listing threads for a specific participant, including logic for querying the database and mapping results to backend thread objects. Their deletion indicates these specific retrieval endpoints are no longer supported or have been replaced by other mechanisms.
(repo-wide) · high confidence
Removal of chat-thread participant-list and get-or-create-for-topic operations
The \chat-thread-participant-list\ operation, which previously retrieved participants for team, party, and direct chat threads, and the \chat-thread-get-or-create-for-topic\ operation, which managed thread creation based on topics, have been removed from the codebase.
svc/pkg/chat-thread/ops/participant-list · high confidence
Removal of cloud device-link worker implementation
The \svc/pkg/cloud/worker\ module has been removed, deleting the main entry point and the \device\_link\_complete\ worker logic. This eliminates the background process that previously handled device linking by creating cloud game tokens and publishing completion messages, effectively removing this specific cloud infrastructure capability from the worker service.
svc/pkg/cloud/worker · high confidence
Removal of development namespace token creation service
The \cloud-namespace-token-development-create\ operation has been removed from the system. This service previously validated development hostnames and ports, created a long-lived token with specific game namespace development entitlements, and persisted the association in the database. Its removal indicates that the capability to generate these specific development tokens is no longer supported or has been replaced by a different mechanism.
svc/pkg/build/standalone/default-create, svc/pkg/cloud/ops/namespace-token-development-create, svc/pkg/cloud/ops/namespace-token-public-create · high confidence
Removal of direct ClickHouse-based log reading operation
The \nomad-log-read\ operation implementation has been removed from the service. This deletes the code that previously queried ClickHouse directly to retrieve Nomad log entries based on allocation, task, and timestamp filters, indicating a shift away from this specific data access pattern.
svc/pkg/nomad-log/ops/read · high confidence
Removal of email sending implementation
The email sending operation logic has been removed from this service. The code that previously handled constructing SendGrid API requests, managing recipients, attachments, and template data is no longer present.
svc/pkg/email/ops/send · high confidence
Removal of email verification completion operation
The implementation for the \email-verification-complete\ operation has been removed from the service. This deletes the logic that previously handled verifying email codes, checking expiration, enforcing attempt limits, and recording completion status in the database.
svc/pkg/email-verification/ops/complete, svc/pkg/team/ops/avatar-upload-complete, svc/pkg/user/ops/avatar-upload-complete · high confidence
Removal of faker game-namespace and game-version operations
The faker operations for creating game namespaces and game versions have been removed from the service. This eliminates the ability to automatically provision test environments for these specific components via the faker tool, likely as part of a cleanup to consolidate or replace these legacy test setup mechanisms.
svc/pkg/faker/ops/game-version · high confidence
Removal of faker matchmaker player and team operations
The faker service no longer provides operations to generate fake matchmaker players or fake teams. The \faker-mm-player\ operation, which previously created fake player tokens and joined them to lobbies, and the \faker-team\ operation, which previously created fake teams with members and developer status, have been deleted from the system.
svc/pkg/faker/ops/mm-player · high confidence
Removal of game creation operation implementation
The implementation for the \game-create\ operation has been removed from the codebase. This operation previously handled the validation of game details, verified the developer team's status, and inserted game records along with their tags into the database before emitting an analytics event.
svc/pkg/game/ops/create · high confidence
Removal of game namespace URL resolution operation
The \game-namespace-resolve-url\ operation has been removed from the service. This operation previously handled the resolution of game and namespace identifiers from URLs by parsing domains (either rivet.game subdomains or custom CDN domains) and querying backend services. Its removal means that URL-based namespace resolution via this specific endpoint is no longer available.
svc/pkg/game/ops/namespace-resolve-url · high confidence
Removal of game version and token validation logic
The \game-version-validate\ and \game-token-development-validate\ operations have been removed from the codebase. This eliminates the server-side validation logic that previously enforced constraints on game version display names, CDN route configurations, and lobby port assignments (including uniqueness, range overlaps, and protocol compatibility).
svc/pkg/game/ops/version-validate · high confidence
Removal of game-user link creation operation
The \game-user-link-create\ operation has been removed from the service. This operation previously generated a temporary link token and recorded the association between a game user and a namespace in the database, along with emitting an analytics event. Its removal indicates that this specific linking workflow is no longer supported or has been replaced by a different mechanism.
(repo-wide) · high confidence
Removal of game-user recommendation operation
The \game-user-recommend\ operation has been removed from the service. The implementation file is deleted, meaning the operation no longer exists to fetch or recommend game users.
svc/pkg/game-user/ops/recommend · high confidence
Removal of hCaptcha configuration retrieval operation
The \captcha-hcaptcha-config-get\ operation has been removed from the service. This operation previously allowed clients to retrieve the hCaptcha site key based on a difficulty level by reading specific environment variables (e.g., \HCAPTCHA\_SITE\_KEY\_EASY\). Its removal means this configuration data is no longer accessible via this API endpoint.
svc/pkg/captcha/ops/hcaptcha-config-get · high confidence
Removal of hCaptcha verification operation
The hCaptcha verification operation (captcha-hcaptcha-verify) has been removed from the system. This change eliminates the ability to verify hCaptcha tokens via this specific service component, as the implementation file containing the verification logic and HTTP client interaction has been deleted.
svc/pkg/captcha/ops/hcaptcha-verify · high confidence
Removal of hardcoded tier listing logic
The \svc/pkg/tier/ops/list\ operation source file has been deleted, removing the server-side logic that previously generated and returned a static list of tier definitions (such as \basic-4d1\, \basic-2d1\, etc.) based on hardcoded resource reservations. This change eliminates the local computation of tier attributes like CPU, memory, and bandwidth from this specific service component.
svc/pkg/tier/ops/list · high confidence
Removal of internal S3 utility library
The \lib/s3-util\ library has been removed from the codebase. This module previously provided an S3 client wrapper that handled endpoint configuration for internal (Consul-based) and external access, including specific logic to resolve Minio's Consul DNS address for job servers. Its removal indicates a shift in how S3 connectivity is managed, likely moving away from the Consul DNS resolution pattern for internal cluster communication.
lib/s3-util · high confidence
Removal of internal utility libraries and service operations
This change removes several internal Rust source files, including the \redis-util\ library (containing Redis result wrappers and search query escaping), various service operations (\cf-turnstile-verify\, \faker-user\, \mm-lobby-list-for-namespace\, \mm-lobby-player-count\, \mm-player-count-for-namespace\, \perf-log-get\), and utility modules (\game-user\, \kv\, \nsfw\). These deletions eliminate the associated code for Cloudflare Turnstile verification, user data generation, multiplayer lobby and player count retrieval, performance log fetching, and key-value store utilities.
(repo-wide) · high confidence
Removal of job utility constants and helpers
The job utility module has been stripped of its previous configuration and helper definitions. Specifically, the hardcoded TCP and UDP port ranges for ingress load balancers (previously 20000–20512 and 26000–26512) have been removed, along with the Redis key generation logic for proxied ports. Additionally, utility functions for identifying Nomad job runs and constants for task cleanup resource limits (CPU and memory) and task names have been deleted from the library.
svc/pkg/job/util · high confidence
Removal of legacy 'build' cache implementation
The \lib/cache/build\ module has been completely removed. This deletion eliminates the previous caching layer, including its error handling, key serialization, request configuration, getter context, and rate-limiting logic, along with its associated integration tests.
lib/cache · high confidence
Removal of legacy API services
The \api-admin\, \api-auth\, \api-cf-verification\, \api-chat\, \api-cloud\, \api-group\, \api-identity\, \api-job\, \api-kv\, \api-matchmaker\, and \api-party\ services have been removed from the system. This change eliminates the service definitions, router configurations, and associated integration tests for these previously distinct API endpoints.
svc · high confidence
Removal of legacy Bolt-based build retrieval operation
The \build-get\ operation implementation in \svc/pkg/build/ops/get\ has been removed. This deletion eliminates the legacy code path that directly queried the \builds\ table via SQLx to retrieve build details (such as game ID, upload ID, and image tag), indicating a migration away from the previous data access pattern or storage backend.
svc/pkg/build/ops/get · high confidence
Removal of legacy Cloud API service and Cloudflare verification service
The \svc/api/cloud\ and \svc/api/cf-verification\ services have been completely removed from the codebase. This deletion eliminates the legacy HTTP endpoints for managing game resources (such as builds, CDNs, matchmaker lobbies, and namespaces) and the Cloudflare custom hostname verification route. Users relying on these specific API endpoints for game cloud management or domain verification will no longer have access to this functionality through these services.
svc/api/cloud · high confidence
Removal of legacy admin API authentication and routes
The legacy admin API service located in \svc/api/admin\ has been removed. This change deletes the previous authentication mechanism, which relied on a static token read from environment variables, and removes the associated route definitions, including the endpoint for converting a group to a developer. Users relying on this specific admin interface will no longer have access to these legacy endpoints.
svc/api/admin · high confidence
Removal of legacy auth and job API services
The \svc/api/auth\ and \svc/api/job\ services have been deleted, removing the endpoints for identity management (including email verification and token refresh) and job run cleanup. This eliminates the legacy authentication middleware, route handlers, and associated utility functions that previously managed user sessions and job lifecycle operations.
svc/api/auth · high confidence
Removal of legacy backend and common Protobuf definitions
The entire \proto/\ directory has been removed, deleting all shared Protobuf definitions including \common.proto\, \claims.proto\, and all backend service schemas (billing, blog, captcha, cdn, chat, cloud, game, identity, job, kv, matchmaker, net, nomad\_log, notification, party, region, team, upload, user, and chirp). This cleanup eliminates the legacy API contract layer that previously defined data structures for services such as the matchmaker, chat, and user identity systems.
proto · high confidence
Removal of legacy chat message and thread listing operations
The \chat-message-list-for-user\ and \chat-thread-recent-for-user\ operations have been removed from the codebase. This deletes the implementation logic that previously fetched chat messages and recent thread lists directly from the database and Redis cache, indicating a migration away from these specific service endpoints.
svc/pkg/chat-message/ops/list-for-user, svc/pkg/chat-thread/ops/recent-for-user · high confidence
Removal of legacy chat, game, group, identity, and party conversion modules
The \lib/convert\ library has removed the \chat\, \game\, \group\, \identity\, and \party\ modules, along with their corresponding \fetch\ modules. This deletion eliminates the code responsible for converting backend protocol buffer data into Smithy API models for these specific domains, effectively removing the legacy conversion logic for chat messages, game summaries, group/team details, user identities, and party states from this library.
lib/convert · high confidence
Removal of legacy cloud namespace-get implementation
The \svc/pkg/cloud/ops/namespace-get\ service, which previously handled fetching cloud namespace details and their associated CDN, matchmaker, KV, and identity configurations, has been removed. This change eliminates the old module code as part of the migration to a single database and macro-based query system, meaning this specific operation entry point is no longer available in its previous form.
svc/pkg/cloud/ops/namespace-get · high confidence
Removal of legacy connection pool library
The \lib/pools\ crate has been completely removed from the codebase. This deletion eliminates the legacy implementation for managing NATS, Redis, and CockroachDB connection pools, along with its associated error types, metrics recording, and transaction retry utilities.
lib/pools · high confidence
Removal of legacy custom hostname retrieval operation
The \cf-custom-hostname-get\ operation implementation has been removed from the service. This deletes the direct SQL query logic that previously fetched custom hostname records (including identifiers, hostnames, and status) from the \custom\_hostnames\ table, indicating a migration away from this specific data access pattern.
svc/pkg/cf-custom-hostname/ops/get · high confidence
Removal of legacy developer team billing collection service
The standalone \billing-collect\ service, which previously handled billing metric aggregation for developer teams, has been removed. This eliminates the legacy logic that queried \dev\_teams\ from the database, aggregated billing metrics via \team\_billing\_aggregate\, and prepared data for Stripe integration.
svc/pkg/team/standalone/billing-collect · high confidence
Removal of legacy follow and mutual friend list operations
The \user-follow-request-list\ and \user-mutual-friend-list\ operations have been removed from the codebase. This deletion eliminates the previous SQL-based implementations for retrieving pending follow requests and mutual friends, which relied on direct \sqlx\ queries against the \user\_follows\ table. Users will no longer have access to these specific legacy endpoints, as the functionality is being consolidated or replaced by the new single-database migration and macro-based query system.
svc/pkg/user-follow/ops/request-list, svc/pkg/user/ops/mutual-friend-list · high confidence
Removal of legacy game namespace and name-id resolution operations
The \game-namespace-get\ and \game-resolve-name-id\ operations have been removed from the service. This eliminates the direct SQL queries against the \game\_namespaces\ and \games\ tables that previously handled namespace retrieval and name-to-ID resolution, indicating a shift in how these lookups are performed within the system.
svc/pkg/game/ops/resolve-name-id · high confidence
Removal of legacy matchmaking utility module
The \svc/pkg/mm/util\ module has been completely removed from the codebase. This deletion eliminates hardcoded constants for lobby and player timeouts, default player capacity limits, and Redis key generation logic for lobby and player configurations. It also removes the \JoinKind\ and \FindQueryStatus\ enums, Nomad port formatting utilities, and version migration definitions that were previously shared across the matchmaking service. Users relying on these internal utilities for custom integrations or extensions will no longer have access to these shared definitions.
svc/pkg/mm/util · high confidence
Removal of legacy operation core library and macros
The \lib/operation/core\ library, including the \Operation\ trait, \OperationContext\, and the \lib/operation/macros\ crate containing the \\#\[operation\]\ procedural macro, has been removed. This eliminates the previous mechanism for defining and invoking operations via the \op!\ macro and associated context handling, indicating a migration to a different operation execution model or framework within the system.
lib/operation · high confidence
Removal of legacy service operation implementations
The implementation files for the \cdn-version-publish\, \faker-mm-lobby-row\, \game-user-create\, and \token-exchange\ operations have been deleted from the repository. This removes the specific Rust logic that previously handled CDN version publishing, matchmaking lobby row generation, game user creation with token issuance, and token exchange via direct SQL queries against CockroachDB. These changes are part of a broader migration to a single database architecture, indicating that the functionality previously managed by these individual service operations is being consolidated or replaced.
(repo-wide) · high confidence
Removal of legacy utility libraries
The \lib/util\ crate and its submodules (\core\, \env\, \macros\, \search\) have been removed from the codebase. This deletion eliminates a wide range of internal helper functions, including input validation (identifiers, display names, domains), string formatting, duration and file-size conversions, UUID parsing, route generation, and environment variable accessors. Any code previously depending on these utilities will need to adopt alternative implementations or dependencies.
lib/util · high confidence
Removal of lib/runtime module
The \lib/runtime\ module, which previously handled Tokio runtime configuration and JSON-based logging setup, has been removed from the codebase. This change eliminates the centralized runtime initialization logic and associated Prometheus metrics for thread counting that were previously exposed through this library.
lib/runtime · high confidence
Removal of lib/schemac source file
The main source file for the schemac library (lib/schemac/src/lib.rs) has been deleted. This removes the library's public API, including the CompileOpts builder, CompilePlugin trait, and schema metadata structures (ModuleMeta, MessageMeta) that were previously used to configure and execute Protobuf schema compilation.
lib/schemac · high confidence
Removal of lib/types build infrastructure and generated schema
The build logic for the \lib/types\ crate has been removed, including the \lib/types/build\ source, the \lib/types/core/build.rs\ build script, and the \lib/types/core/src/lib.rs\ file that previously included the generated \schema.rs\. This deletion eliminates the custom Protobuf compilation pipeline (which utilized \schemac\ and specific plugins like \CommonPlugin\ and \BackendMessagePlugin\) and the static \uuid\_expanded.rs\ template used to handle UUID serialization. Consequently, the \lib/types\ crate no longer generates or exposes the schema types that were previously produced by this build process.
lib/types · high confidence
Removal of lobby find try-complete operation
The \mm-lobby-find-try-complete\ operation has been removed from the codebase. This operation previously handled the completion of matchmaking queries by validating their state in Redis, checking lobby readiness, removing query data from Redis, updating the query status in the database, and publishing completion messages. Its removal indicates that this specific mechanism for finalizing lobby find queries is no longer part of the service's functionality.
(repo-wide) · high confidence
Removal of lobby idle-update operation implementation
The source file for the \mm-lobby-idle-update\ operation has been deleted, removing the logic that managed pools of idle lobbies. This operation previously fetched namespace and region configurations to determine minimum and maximum idle lobby counts, executed a Lua script against Redis to identify which lobbies to create or stop, and subsequently triggered \lobby\_create\ or \lobby\_stop\ messages. With this file removed, the system no longer performs this specific automated idle-lobby maintenance routine.
(repo-wide) · high confidence
Removal of matchmaker API service source code
The source code for the matchmaker API service located in \svc/api/matchmaker\ has been completely removed. This deletion eliminates the implementation of core matchmaking endpoints, including lobby management (ready, join, find, closed, list), player connection tracking (connected, disconnected, statistics), and region listing. Consequently, the service's authentication logic, route definitions, and utility functions are no longer present in this location.
svc/api/matchmaker · high confidence
Removal of party, member, and invite operations and utilities
The party service has removed the implementation for retrieving party details, listing and getting party members, and managing party invites (including alias lookup). Additionally, the Redis population standalone tool and the shared utility modules defining party key structures and state enums have been deleted, effectively disabling all party-related data retrieval and management capabilities in this service.
(repo-wide) · high confidence
Removal of pending-delete-toggle operation implementation
The implementation for the \pending-delete-toggle\ operation has been removed from the codebase. This operation previously handled the logic for toggling a user's pending deletion status by verifying their identity, updating the \delete\_request\_ts\ field in the database, and publishing a message to update the user record. Its removal indicates that this specific functionality is no longer supported or has been replaced by a different mechanism.
svc/pkg/cloud/ops/version-get, svc/pkg/team/ops/get · high confidence
Removal of region configuration utility
The region configuration loading logic has been removed from the region utility package. Specifically, the \config.rs\ module, which previously read and parsed \region-config.json\ from the Nomad task directory into a map of \Region\ structs, has been deleted. Consequently, the \config\ module is no longer exported from the package's \lib.rs\, meaning consumers of this utility can no longer access region configuration data through this specific interface.
svc/pkg/region/util · high confidence
Removal of region recommendation logic
The \region-recommend\ operation implementation has been removed from the codebase. This deletes the logic that previously recommended regions based on user coordinates or IP address by calculating distances to available servers, effectively disabling this specific recommendation capability.
svc/pkg/region/ops/recommend · high confidence
Removal of several internal operation handlers
The \cdn-version-prepare\, \cloud-device-link-create\, \faker-cdn-site\, \identity-config-version-prepare\, \kv-config-version-prepare\, and \mm-dev-player-token-create\ operation handlers have been removed from the codebase. This deletion eliminates the backend logic for preparing CDN and configuration versions, creating cloud device links, generating fake CDN site data, and creating development player tokens for the matchmaker.
(repo-wide) · high confidence
Removal of standalone CDN and Identity Config version-get operations
The dedicated \cdn-version-get\ and \identity-config-version-get\ operations have been removed from the codebase. This change eliminates the specific Rust implementations that previously queried the \game\_versions\, \game\_version\_custom\_headers\, \custom\_display\_names\, and \custom\_avatars\ tables to retrieve CDN routing rules and identity customizations. Users relying on these specific operation endpoints will no longer have access to this data retrieval path, indicating a migration to a different mechanism for fetching version configurations.
svc/pkg/cdn/ops/version-get, svc/pkg/identity-config/ops/version-get · high confidence
Removal of standalone allocation and evaluation monitors
The standalone services for monitoring Nomad allocation updates (alloc-update-monitor) and evaluation updates (eval-update-monitor) have been removed. This eliminates the dedicated background processes that previously listened for these specific Nomad events and forwarded them via internal messages, indicating a consolidation or architectural shift in how Nomad state changes are processed.
svc/pkg/job-run/standalone/alloc-update-monitor, svc/pkg/job-run/standalone/eval-update-monitor · high confidence
Removal of standalone health-check service library
The standalone health-check library (\lib/health-checks\) has been removed from the codebase. This library previously provided a standalone HTTP server (using Hyper) to expose health endpoints for CRDB, Redis, NATS, and liveness checks. Its removal indicates that this specific standalone service component is no longer part of the product architecture.
lib/health-checks · high confidence
Removal of standalone metrics server and histogram buckets
The metrics library no longer exposes a standalone HTTP server for exporting Prometheus metrics, nor does it provide the predefined histogram bucket configuration. Specifically, the \run\_standalone\ function, the \BUCKETS\ constant, and the internal modules (\server.rs\, \buckets.rs\) have been removed from the public API, meaning users can no longer start a separate metrics endpoint or rely on these specific histogram boundaries from this crate.
lib/metrics · high confidence
Removal of standalone pending user deletion service
The standalone service responsible for deleting pending users (svc/pkg/user/standalone/delete-pending) has been removed. This eliminates the background process that queried the database for users with pending deletion requests older than 30 days and published delete messages, indicating that this specific cleanup logic is no longer executed via this standalone component.
svc/pkg/user/standalone/delete-pending · high confidence
Removal of standalone upload file-list operation
The dedicated \upload-file-list\ operation implementation has been removed from the codebase. This change eliminates the specific logic that queried the \upload\_files\ table to retrieve file metadata (path, MIME type, content length) for a given set of upload IDs, indicating that this functionality is no longer handled by this specific service component.
svc/pkg/upload/ops/file-list · high confidence
Removal of team member relationship retrieval operation
The \team-member-relationship-get\ operation has been removed from the codebase. This operation previously allowed clients to query shared team memberships between user pairs by executing a SQL query against the \team\_members\ table. Its removal means this specific capability to retrieve mutual team IDs for user pairs is no longer available via this service endpoint.
svc/pkg/team/ops/member-relationship-get · high confidence
Removal of team member retrieval operation implementation
The implementation for the \team-member-get\ operation has been removed from the codebase. This change eliminates the logic responsible for querying and returning team member details (team ID, user ID, and join timestamp) from the database, effectively disabling this specific data retrieval capability within the team service.
svc/pkg/team/ops/member-get · high confidence
Removal of team-invite worker implementation
The \svc/pkg/team-invite/worker\ service has been completely removed from the codebase. This deletion eliminates the legacy Rust-based workers responsible for generating team invitation codes (\create\) and processing their consumption (\consume\), including the associated database transaction logic and member-validation checks. Users relying on this specific worker component for team invitation workflows will no longer have access to this implementation.
svc/pkg/chat-message/worker, svc/pkg/team-invite/worker · high confidence
Removal of team-invite worker service
The \svc/pkg/team-invite/worker\ service has been completely removed from the codebase. This deletion eliminates the standalone Rust worker that previously handled the creation of invitation codes and the consumption of those invites to add users to teams. Consequently, the logic for generating unique invite codes, validating their expiration and usage limits, and triggering the subsequent team membership creation messages is no longer present in this specific service location.
(repo-wide) · high confidence
Removal of the Chirp client library and worker framework
The \lib/chirp\ directory has been completely removed, deleting the entire Chirp client library, worker framework, and associated tooling. This includes the \chirp\_client\ crate (handling NATS and Redis communication, message serialization, and RPC logic), the \chirp\_worker\ crate (managing worker lifecycles, configuration, and request handling), the \chirp\_worker\_attributes\ proc-macro crate (providing the \\#\[worker\]\ attribute), and supporting modules for metrics, performance context, and type definitions. Users of this library will no longer have access to these components for inter-service communication or worker management.
lib/chirp · high confidence
Removal of the api-status service and its matchmaker health-check endpoint
The api-status service has been completely removed from the codebase. This eliminates the /matchmaker endpoint that previously performed health checks against individual game nodes by creating temporary bypass tokens and querying the matchmaker service. Users relying on this specific status check for matchmaker availability will no longer have access to this data through this service.
svc/api/status · high confidence
Removal of the global-error library
The \lib/global-error\ crate has been completely removed from the codebase. This deletion eliminates the \GlobalError\ and \GlobalResult\ types, along with associated helper modules (\ext\, \macros\) and utility structs like \Location\. Consequently, any code previously relying on this library's error handling macros (such as \err\_code\, \internal\_panic\, \retry\_panic\) or error conversion traits must be updated to use the new error handling mechanisms.
(repo-wide) · high confidence
Removal of the legacy identity API service
The entire \svc/api/identity\ service has been removed, eliminating the legacy HTTP endpoints for user identity management, authentication, and social features. This deletion removes the codebase responsible for identity setup, profile management, avatar uploads, user following, activity tracking, and the real-time event feed (chat, parties, matchmaker lobbies). Consequently, clients can no longer interact with these specific identity-related API routes.
svc/api/chat, svc/api/group · high confidence
Removal of the lib/connection crate
The \lib/connection\ crate has been deleted, removing the centralized \Connection\ struct that previously aggregated the Chirp client, Rivet pools, and cache into a single handle. This eliminates the convenience methods for accessing specific Redis pools (such as \redis-cache\, \redis-cdn\, \redis-job\, \redis-mm\, \redis-party\, \redis-user-presence\, and \redis-search\) and the \crdb\ pool accessor, as well as the \wrap\ method used to propagate tracing context between operations. Consumers of this library must now manage these dependencies directly or use alternative connection mechanisms.
lib/connection · high confidence
Removal of the standalone KV API service
The standalone \svc/api/kv\ service has been removed from the codebase. This change eliminates the previous implementation of the Key-Value store API, including its authentication middleware, route handlers for single and batch operations (GET, PUT, DELETE, LIST), and associated utility functions. Users relying on this specific service endpoint will no longer have access to these KV operations through this location, as the functionality is being consolidated or replaced by the new API monolith architecture.
svc/api/kv · high confidence
Removal of the standalone MM garbage collection service
The standalone garbage collection service (\svc/pkg/mm/standalone/gc\) has been removed. This service previously handled the periodic cleanup of unready lobbies and unregistered players by querying Redis and sending stop/remove messages. Its removal indicates that this cleanup logic is no longer managed by this specific standalone process, likely having been migrated to other services or handled differently within the system.
svc/pkg/job/standalone/gc, svc/pkg/mm/standalone/gc-full, svc/pkg/user-presence/standalone/gc · high confidence
Removal of the standalone game-logic garbage collection service
The \svc/pkg/mm/standalone/gc\ service has been deleted, removing the standalone component responsible for periodically culling unready lobbies and unregistered players from the matchmaking system. This eliminates the background tasks that previously queried Redis for stale lobby and player states and triggered their removal via Chirp messages, indicating that this cleanup logic has been migrated to other services or handled differently.
svc/pkg/mm/standalone/gc · high confidence
Removal of the upload-delete worker
The upload-delete worker, which previously handled the deletion of upload files from S3 buckets and updated the database status, has been removed from the service. This change eliminates the code responsible for querying upload records, batching S3 object deletions, and marking uploads as deleted.
svc/pkg/upload/worker · high confidence
Removal of token creation and revocation service implementations
The implementation files for the token creation (\token-create\) and token revocation (\token-revoke\) operations have been deleted from the repository. This removes the code responsible for generating JWTs, managing session states, handling refresh token logic, and marking tokens as revoked in the database. Users relying on these specific service endpoints for token lifecycle management will no longer have access to these functionalities within this package.
svc/pkg/token/ops/create · high confidence
Removal of user identity deletion operation
The \user-identity-delete\ operation has been removed from the codebase. This eliminates the functionality that previously deleted email records associated with specific user IDs from the \emails\ table in the \db-user-identity\ database.
svc/pkg/user-identity/ops/delete · high confidence
Removal of user profile validation logic
The \user-profile-validate\ operation implementation has been removed from the codebase. This change eliminates the server-side validation for user display names, account numbers, and biographies, as well as the logic that checked for handle uniqueness against the database.
svc/pkg/user/ops/profile-validate · high confidence
Removal of user-follow request ignore worker
The worker responsible for processing user-follow request ignore operations has been removed from the service. This eliminates the background job that previously updated the \user\_follows\ table to mark specific follow requests as ignored and emitted a completion message, effectively disabling the ability to ignore follow requests via this specific worker component.
svc/pkg/user-follow/worker · high confidence
Removal of user-presence service operations
The \user-presence-get\ and \user-presence-touch\ operations have been removed from the system. This eliminates the ability to query user presence status and game activity via Redis, as well as the mechanism for updating presence timestamps and triggering arrival messages.
svc/pkg/user-presence/ops/get · high confidence
Removal of user-presence utility module
The \svc/pkg/user-presence/util\ package has been removed, deleting the \key.rs\ and \lib.rs\ source files. This eliminates the helper functions for generating Redis keys (such as \user\_presence\ and \game\_activity\) and the \State\ structs for serializing user presence and game activity data, along with the defined TTL constant.
svc/pkg/user-presence/util · high confidence
Removed Linode server provisioning module
The Terraform module for provisioning Linode instances has been completely removed from the infrastructure codebase. This deletion eliminates the ability to create Linode virtual servers, associated SSH keys, root passwords, boot disks, swap partitions, and network firewalls via this module. Users relying on this module for Linode-based server deployments will no longer be able to provision or manage these resources through this specific infrastructure path.
_infra/tf/modules/generic\server · high confidence
Removed game and team recommendation operations
The \game-recommend\, \team-member-count\, and \team-recommend\ operations have been removed from the codebase. This eliminates the server-side logic that previously fetched all games, counted members for specific teams, and recommended teams based on creation timestamp, effectively disabling these recommendation features for users.
svc/pkg/game/ops/recommend, svc/pkg/team/ops/member-count, svc/pkg/team/ops/recommend · high confidence
Removed game banner and logo upload completion operations
The \game-banner-upload-complete\ and \game-logo-upload-complete\ operations have been removed from the system. These services previously handled the finalization of banner and logo uploads by confirming the upload, updating the corresponding \banner\_upload\_id\ or \logo\_upload\_id\ in the \games\ table, and triggering an update message. Their removal indicates a shift in how game asset uploads are finalized, likely consolidating this logic into a different service or workflow.
svc/pkg/game/ops/banner-upload-complete, svc/pkg/game/ops/logo-upload-complete · high confidence
Removed generated Rust SDK code for the api-auth service
The generated Rust client library for the \api-auth\ service has been removed from the \lib/smithy-output\ directory. This deletion eliminates the auto-generated source files (including models, client, config, error handling, and serialization logic) that previously provided an SDK for interacting with authentication endpoints such as email verification and identity token refresh. Users relying on this specific generated Rust client will no longer have access to these bindings.
lib/smithy-output · high confidence
Removed push notification worker implementation
The push notification worker service, including its main entry point and the logic for sending Firebase Cloud Messaging (FCM) notifications, has been removed from the codebase. This deletion eliminates the component responsible for processing push notification creation messages and delivering them to users via Firebase.
svc/pkg/push-notification/worker · high confidence
Removed user-notification-auth register and unregister operations
The \user-notification-auth-register\ and \user-notification-auth-unregister\ service operations have been removed from the codebase. This eliminates the direct database interactions for upserting and deleting Firebase access keys in the \users\ table, indicating that this functionality is no longer handled by these specific service endpoints.
svc/pkg/user-notification-auth/ops/register, svc/pkg/user-notification-auth/ops/unregister · high confidence
Behavioural changes
1 commit (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 1 commit, 141 files: “update”. Also in this area: Kitchen-sink example expanded with comprehensive actor lifecycle and integration demos.
(repo-wide) · low confidence · unverified
1 commit (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 1 commit, 281 files: “update”.
(repo-wide) · medium confidence · unverified
1 commit (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 1 commit, 397 files: “update”.
(repo-wide) · low confidence · unverified
1 commit (0 fixes) modifying engine/sdks/rust/migrate-from-v2-protocol, engine/sdks/schemas/migrate-from-v2-protocol
A change to existing behaviour in engine/sdks/rust/migrate-from-v2-protocol, engine/sdks/schemas/migrate-from-v2-protocol — 1 commit, 4 files: “update”.
engine/sdks/rust/migrate-from-v2-protocol, engine/sdks/schemas/migrate-from-v2-protocol · medium confidence · unverified
1 commit (0 fixes) modifying examples/workflow-sdk
A change to existing behaviour in examples/workflow-sdk — 1 commit, 6 files: “refactor(integrations): rename vercel-world to workflow-world and align docs with Workflow SDK”.
examples/workflow-sdk · medium confidence · unverified
1 commit (0 fixes) modifying shared/typescript/shared-data
A change to existing behaviour in shared/typescript/shared-data — 1 commit, 2 files: “update”.
shared/typescript/shared-data · medium confidence · unverified
107 commits (14 fixes) modifying lib/bolt/config/src
A change to existing behaviour in lib/bolt/config/src — 107 commits (14 fixs), 6 files: “Impl public/private cluster toggle”; “WIP”; “Finish grafana tunnel”; and 104 more (refs \#932, \#898, \#389, \#974, \#979, …).
lib/bolt/config/src · medium confidence · unverified
11 commits (0 fixes) modifying engine/packages/api-public-shim
A change to existing behaviour in engine/packages/api-public-shim — 11 commits, 3 files: “update”.
engine/packages/api-public-shim · medium confidence · unverified
11 commits (0 fixes) modifying engine/packages/depot-worker
A change to existing behaviour in engine/packages/depot-worker — 11 commits, 224 files: “update”.
engine/packages/depot-worker · medium confidence · unverified
11 commits (0 fixes) modifying engine/packages/pegboard/src/actor\_machine
A change to existing behaviour in engine/packages/pegboard/src/actor\_machine — 11 commits, 2 files: “update”.
_engine/packages/pegboard/src/actor\machine · medium confidence · unverified
11 commits (1 fix) modifying infra/tf/nomad
A change to existing behaviour in infra/tf/nomad — 11 commits (1 fix), 9 files: “move redis to its own plan, add multipl redis containers”; “WIP”; “Fix exposed ports, migrate redis-exporter to k8s”; and 7 more.
infra/tf/nomad · medium confidence · unverified
11 commits (1 fix) modifying infra/tf/pools
A change to existing behaviour in infra/tf/pools — 11 commits (1 fix), 7 files: “impl install script for job”; “Implement server provisioning (\#300)”; “WIP rework networking”; and 8 more (refs \#300, \#1216).
infra/tf/pools · medium confidence · unverified
12 commits (0 fixes) modifying engine/packages/depot-client/src
A change to existing behaviour in engine/packages/depot-client/src — 12 commits, 12 files: “update”; “chroe: rename rivetkit-sqlite to depot-client”; “refactor(depot-client): split embedded depot transport”; and 3 more (refs \#5198).
engine/packages/depot-client/src · medium confidence · unverified
12 commits (3 fixes) modifying rivetkit-rust/packages/engine-process
A change to existing behaviour in rivetkit-rust/packages/engine-process — 12 commits (3 fixs), 2 files: “update”; “fix(rivetkit): restore local engine development thresholds”; “\[SLOP(gpt-5)\] feat(cli): add rivetkit cli”; and 5 more (refs \#5483, \#5780, \#5648).
rivetkit-rust/packages/engine-process · medium confidence · unverified
12 commits (4 fixes) modifying engine/packages/api-types
A change to existing behaviour in engine/packages/api-types — 12 commits (4 fixs), 24 files: “update”; “feat(engine): actors lifecycle testing (\#3623)”; “chore: setup rivet-engine api tests (\#3540)”; and 9 more (refs \#3623, \#3540, \#4547, \#3610, \#4556, …).
engine/packages/api-types · medium confidence · unverified
12 commits (5 fixes) modifying engine/packages/runtime
A change to existing behaviour in engine/packages/runtime — 12 commits (5 fixs), 4 files: “\[SLOP(claude-opus-4-8)\] feat: upstream OSS-safe engine + rivetkit changes from EE”; “update”; “fix: add TOKIO\_WORKER\_THREADS\_SUBTRACT, break earlier when allocating pending actors (\#3774)”; and 9 more (refs \#3774, \#3239, \#3290, \#3443, \#3656, …).
engine/packages/runtime · medium confidence · unverified
14 commits (3 fixes) modifying engine/sdks/rust/data/src/versioned
A change to existing behaviour in engine/sdks/rust/data/src/versioned — 14 commits (3 fixs), 23 files: “update”; “fix(pb): simplify runner wf (\#3483)”; “chore: fix remaining issues with rivetkit-core”; and 4 more (refs \#3483, \#3239, \#3275, \#5780, \#3528).
engine/sdks/rust/data/src/versioned · medium confidence · unverified
141 commits (35 fixes) modifying lib/bolt/core/src/dep/terraform
A change to existing behaviour in lib/bolt/core/src/dep/terraform — 141 commits (35 fixs), 10 files: “Fix Linode tags”; “Set up client tunnels”; “WIP - Nathan fixed build after rebase”; and 132 more (refs \#1018, \#979, \#534, \#341, \#945, …).
lib/bolt/core/src/dep/terraform · medium confidence · unverified
15 commits (0 fixes) modifying gen/openapi/internal/rust/src/apis
A change to existing behaviour in gen/openapi/internal/rust/src/apis — 15 commits, 40 files: “WIP create custom lobby endpoint”; “Update Fern”; “Remove api-chat”; and 11 more.
gen/openapi/internal/rust/src/apis · medium confidence · unverified
15 commits (2 fixes) modifying lib/bolt/core/src/dep
A change to existing behaviour in lib/bolt/core/src/dep — 15 commits (2 fixs), 2 files: “Remove Cloudflare tunnel”; “Fix source hash calculation (\#492)”; “WIP k8s gen”; and 12 more (refs \#492, \#490, \#486, \#1216).
lib/bolt/core/src/dep · medium confidence · unverified
16 commits (5 fixes) modifying infra/tf/dns
A change to existing behaviour in infra/tf/dns — 16 commits (5 fixs), 4 files: “Fix dns records”; “Implement server provisioning (\#300)”; “Switch from AWS ELB to NLB to fix surge queue length (\#335)”; and 13 more (refs \#300, \#335, \#567, \#1064, \#535, …).
infra/tf/dns · medium confidence · unverified
17 commits (4 fixes) modifying infra/tf/s3\_minio
A change to existing behaviour in infra/tf/s3\_minio — 17 commits (4 fixs), 4 files: “Expose minio to traefik”; “Clean up minio config for local port”; “Implement server provisioning (\#300)”; and 14 more (refs \#300, \#1211).
_infra/tf/s3\minio · medium confidence · unverified
170 commits (46 fixes) modifying lib/bolt/core/src/tasks
A change to existing behaviour in lib/bolt/core/src/tasks — 170 commits (46 fixs), 11 files: “feat(workflows): allow changing tags in workflow (\#962)”; “feat(bolt): add lost servers list and prune commands (\#1096)”; “fix(worfklows): add silence ts (\#1129)”; and 164 more (refs \#962, \#1096, \#1129, \#947, \#898, …).
lib/bolt/core/src/tasks · medium confidence · unverified
19 commits (3 fixes) modifying lib/bolt/core/src/dep/salt
A change to existing behaviour in lib/bolt/core/src/dep/salt — 19 commits (3 fixs), 4 files: “Fix region config”; “Add database dependencies to services”; “Capture events in bg”; and 16 more.
lib/bolt/core/src/dep/salt · medium confidence · unverified
196 commits (59 fixes) modifying lib/bolt/core/src/context
A change to existing behaviour in lib/bolt/core/src/context — 196 commits (59 fixs), 4 files: “Impl public/private cluster toggle”; “Fix remaining errors”; “Fix s3\_credential code”; and 187 more (refs \#1018, \#898, \#1176, \#660, \#389, …).
lib/bolt/core/src/context · medium confidence · unverified
2 commits (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 2 commits, 20 files: “Remove master & nebula”; “👾”.
(repo-wide) · medium confidence · unverified
2 commits (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 2 commits, 33 files: “update”.
(repo-wide) · medium confidence · unverified
2 commits (0 fixes) modifying engine/packages/api-public/src/runner\_pools, engine/packages/sqlite-embedded-filesystem, engine/packages/sqlite-prefetch
A change to existing behaviour in engine/packages/api-public/src/runner\_pools, engine/packages/sqlite-embedded-filesystem, engine/packages/sqlite-prefetch — 2 commits, 33 files: “update”.
_engine/packages/api-public/src/runner\pools, engine/packages/sqlite-embedded-filesystem, engine/packages/sqlite-prefetch · medium confidence · unverified
2 commits (0 fixes) modifying examples/collaborative-document-ot
A change to existing behaviour in examples/collaborative-document-ot — 2 commits, 11 files: “docs(guides): add realtime, cron, and per-tenant database guides (\#5920)”; “update” (refs \#5920).
examples/collaborative-document-ot · medium confidence · unverified
2 commits (0 fixes) modifying integrations/workflow-world
A change to existing behaviour in integrations/workflow-world — 2 commits, 10 files: “update”; “refactor(integrations): rename vercel-world to workflow-world and align docs with Workflow SDK”.
integrations/workflow-world · medium confidence · unverified
20 commits (2 fixes) modifying lib/bolt/cli/src
A change to existing behaviour in lib/bolt/cli/src — 20 commits (2 fixs), 1 file: “Add configuring deploy confirmation to namespace config (\#387)”; “chore: move bolt cluster subcommand to root (\#803)”; “Fix telemetry not always waiting”; and 17 more (refs \#387, \#803, \#790, \#1211, \#391, …).
lib/bolt/cli/src · medium confidence · unverified
23 commits (5 fixes) modifying infra/tf/tls
A change to existing behaviour in infra/tf/tls — 23 commits (5 fixs), 7 files: “Set up client tunnels”; “Implement server provisioning (\#300)”; “WIP”; and 19 more (refs \#300, \#741, \#1211, \#635, \#1064, …).
infra/tf/tls · medium confidence · unverified
23 commits (9 fixes) modifying lib/api-helper/macros
A change to existing behaviour in lib/api-helper/macros — 23 commits (9 fixs), 2 files: “feat(bolt): update datacenters from CLI (\#727)”; “Add admin login system”; “Implement server provisioning (\#300)”; and 20 more (refs \#727, \#300, \#1222, \#1094, \#740, …).
lib/api-helper/macros · medium confidence · unverified
24 commits (7 fixes) modifying examples/kitchen-sink
A change to existing behaviour in examples/kitchen-sink — 24 commits (7 fixs), 10 files: “chore: fmt”; “chore: rivetkit to rust”; “chore: rivetkit core/napi/typescript follow up review”; and 21 more (refs \#3799, \#5198, \#3603, \#3859, \#4477, …).
examples/kitchen-sink · medium confidence · unverified
25 commits (0 fixes) modifying gen/openapi/internal/rust
A change to existing behaviour in gen/openapi/internal/rust — 25 commits, 7 files: “WIP create custom lobby endpoint”; “Update Fern”; “Remove api-chat”; and 21 more.
gen/openapi/internal/rust · medium confidence · unverified
26 commits (6 fixes) modifying engine/packages/api-public/src
A change to existing behaviour in engine/packages/api-public/src — 26 commits (6 fixs), 11 files: “update”; “chore: setup rivet-engine api tests (\#3540)”; “feat(envoy-client): fully flesh out tunnel impl (\#4547)”; and 22 more (refs \#3540, \#4547, \#4556, \#4337, \#4544, …).
engine/packages/api-public/src · medium confidence · unverified
27 commits (7 fixes) modifying engine/packages/pegboard-envoy/src
A change to existing behaviour in engine/packages/pegboard-envoy/src — 27 commits (7 fixs), 12 files: “fix(pb-envoy): hard abort ws to tunnel on ping error”; “\[SLOP(claude-opus-4-8)\] feat: upstream OSS-safe engine + rivetkit changes from EE”; “update”; and 13 more (refs \#4875, \#4463, \#4872).
engine/packages/pegboard-envoy/src · medium confidence · unverified
3 commits (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 3 commits, 65 files: “update”.
(repo-wide) · medium confidence · unverified
3 commits (0 fixes) modifying engine/packages/rivet-sqlite-types, engine/packages/universalpubsub/src/pubsub/stream
A change to existing behaviour in engine/packages/rivet-sqlite-types, engine/packages/universalpubsub/src/pubsub/stream — 3 commits, 4 files: “update”.
engine/packages/rivet-sqlite-types, engine/packages/universalpubsub/src/pubsub/stream · medium confidence · unverified
3 commits (0 fixes) modifying examples/turso
A change to existing behaviour in examples/turso — 3 commits, 6 files: “docs(integrations): add Turso guide and example (\#5941)”; “update” (refs \#5941).
examples/turso · medium confidence · unverified
3 commits (0 fixes) modifying infra/tf/master\_cluster, infra/tf/modules/install\_nebula
A change to existing behaviour in infra/tf/master\_cluster, infra/tf/modules/install\_nebula — 3 commits, 11 files: “Remove IPv6 inbound for Nebula”; “Remove master & nebula”; “👾”.
_infra/tf/master\_cluster, infra/tf/modules/install\nebula · medium confidence · unverified
3 commits (1 fix) modifying engine/packages/outbound-guard
A change to existing behaviour in engine/packages/outbound-guard — 3 commits (1 fix), 3 files: “update”; “feat(outbound): gate serverless outbound requests behind an SSRF policy”; “fix(outbound): allow first-party hosts through the outbound destination policy”.
engine/packages/outbound-guard · medium confidence · unverified
3 commits (1 fix) modifying integrations/flue-runtime
A change to existing behaviour in integrations/flue-runtime — 3 commits (1 fix), 19 files: “feat(flue): stream responses end to end (\#5470)”; “feat(integrations): add Flue support (\#5465)”; “revert(http): return main to Envoy protocol v6 (\#5515)” (refs \#5470, \#5465, \#5515).
integrations/flue-runtime · medium confidence · unverified
30 commits (13 fixes) modifying engine/packages/api-public/src/actors
A change to existing behaviour in engine/packages/api-public/src/actors — 30 commits (13 fixs), 10 files: “fix(api): throw error for invalid id list in query (\#3812)”; “fix: day 1 patch, add dashboards (\#3927)”; “update”; and 26 more (refs \#3812, \#3927, \#3540, \#4547, \#3610, …).
engine/packages/api-public/src/actors · medium confidence · unverified
30 commits (8 fixes) modifying infra/salt/salt
A change to existing behaviour in infra/salt/salt — 30 commits (8 fixs), 113 files: “Fix formatting error in Salt”; “Update deps”; “Update Nomad”; and 25 more.
infra/salt/salt · medium confidence · unverified
32 commits (8 fixes) modifying lib/bolt/core/src/dep/nomad
A change to existing behaviour in lib/bolt/core/src/dep/nomad — 32 commits (8 fixs), 6 files: “Fix default logging disabled state”; “Add backfill service”; “Remove Nomad”; and 29 more.
lib/bolt/core/src/dep/nomad · medium confidence · unverified
33 commits (5 fixes) modifying examples/kitchen-sink/src
A change to existing behaviour in examples/kitchen-sink/src — 33 commits (5 fixs), 4 files: “feat(rivetkit): expose runtime diagnostics”; “\[SLOP(claude-opus-4-8)\] fix(kitchen-sink): serve built frontend from server”; “test(kitchen-sink): add sqlite memory soak harness”; and 30 more (refs \#3799, \#5198, \#5270, \#5780, \#4477, …).
examples/kitchen-sink/src · medium confidence · unverified
37 commits (1 fix) modifying gen/openapi/internal/rust/src/models
A change to existing behaviour in gen/openapi/internal/rust/src/models — 37 commits (1 fix), 342 files: “WIP create custom lobby endpoint”; “Update Fern”; “Allow toggling multipart uploads”; and 33 more (refs \#306, \#314, \#307, \#301, \#304).
gen/openapi/internal/rust/src/models · medium confidence · unverified
4 commits (0 fixes) modifying engine/packages/pegboard-v2-migrator
A change to existing behaviour in engine/packages/pegboard-v2-migrator — 4 commits, 22 files: “update”.
engine/packages/pegboard-v2-migrator · medium confidence · unverified
4 commits (0 fixes) modifying engine/packages/universalpubsub/src/pubsub
A change to existing behaviour in engine/packages/universalpubsub/src/pubsub — 4 commits, 9 files: “update”.
engine/packages/universalpubsub/src/pubsub · medium confidence · unverified
4 commits (0 fixes) modifying lib/bolt/core/src/dep/s3
A change to existing behaviour in lib/bolt/core/src/dep/s3 — 4 commits, 1 file: “WIP”; “WIP get cargo building in docker container”; “Add provider property to uploads, add service build bucket”; and 1 more.
lib/bolt/core/src/dep/s3 · medium confidence · unverified
4 commits (0 fixes) modifying lib/bolt/core/src/tasks/infra/migrate
A change to existing behaviour in lib/bolt/core/src/tasks/infra/migrate — 4 commits, 2 files: “Provision pools again”; “update migration script”; “chore: move bolt cli (\#1216)”; and 1 more (refs \#1216).
lib/bolt/core/src/tasks/infra/migrate · medium confidence · unverified
4 commits (0 fixes) modifying rivetkit-typescript/packages/cli
A change to existing behaviour in rivetkit-typescript/packages/cli — 4 commits, 3 files: “update”; “\[SLOP(gpt-5)\] feat(cli): add rivetkit cli”.
rivetkit-typescript/packages/cli · medium confidence · unverified
4 commits (1 fix) modifying infra/tf/s3\_backblaze
A change to existing behaviour in infra/tf/s3\_backblaze — 4 commits (1 fix), 4 files: “B2 file lock hotfix”; “chore: update bolt with new service definition (\#1211)”; “ATS running”; and 1 more (refs \#1211).
_infra/tf/s3\backblaze · medium confidence · unverified
4 commits (1 fix) modifying lib/bolt/core/src/dep/docker
A change to existing behaviour in lib/bolt/core/src/dep/docker — 4 commits (1 fix), 3 files: “Fix source hash calculation (\#492)”; “Implement docker hub registry for faster start times (\#491)”; “chore: move bolt cli (\#1216)”; and 1 more (refs \#492, \#491, \#1216).
lib/bolt/core/src/dep/docker · medium confidence · unverified
41 commits (12 fixes) modifying lib/api-helper/build/src
A change to existing behaviour in lib/api-helper/build/src — 41 commits (12 fixs), 9 files: “fix: add patch to CORS (\#848)”; “feat(workflows): add api ctx for workflows (\#865)”; “Implement server provisioning (\#300)”; and 38 more (refs \#848, \#865, \#300, \#779, \#670, …).
lib/api-helper/build/src · medium confidence · unverified
42 commits (9 fixes) modifying lib/bolt/core/src/tasks/config
A change to existing behaviour in lib/bolt/core/src/tasks/config — 42 commits (9 fixs), 3 files: “WIP”; “Add admin login flag (\#389)”; “Redis Aiven provider (\#341)”; and 37 more (refs \#389, \#341, \#300, \#779, \#650, …).
lib/bolt/core/src/tasks/config · medium confidence · unverified
43 commits (13 fixes) modifying lib/bolt/core/src/dep/cargo
A change to existing behaviour in lib/bolt/core/src/dep/cargo — 43 commits (13 fixs), 2 files: “feat(bolt): run tests in containers (\#947)”; “fix: get mm tests working again with provisioning (\#711)”; “Fix dns records”; and 40 more (refs \#947, \#711, \#945, \#769, \#300, …).
lib/bolt/core/src/dep/cargo · medium confidence · unverified
44 commits (12 fixes) modifying lib/bolt/core/src/utils
A change to existing behaviour in lib/bolt/core/src/utils — 44 commits (12 fixs), 4 files: “fix(worfklows): add silence ts (\#1129)”; “Fix region config”; “fix(bolt): fix wf commands sql connection on distributed clusters, add errors to history command (\#1197)”; and 41 more (refs \#1129, \#1197, \#579, \#779, \#492, …).
lib/bolt/core/src/utils · medium confidence · unverified
48 commits (13 fixes) modifying lib/bolt/cli/src/commands
A change to existing behaviour in lib/bolt/cli/src/commands — 48 commits (13 fixs), 14 files: “Fix Cargo dependencies”; “Rename dont\_purge -\> no\_purge”; “Implement server provisioning (\#300)”; and 45 more (refs \#300, \#779, \#650, \#492, \#491, …).
lib/bolt/cli/src/commands · medium confidence · unverified
48 commits (5 fixes) modifying lib/bolt/core/src/tasks/infra
A change to existing behaviour in lib/bolt/core/src/tasks/infra — 48 commits (5 fixs), 1 file: “WIP - Nathan fixed build after rebase”; “feat(infra): auto-create dev tunnel & public ip (\#979)”; “Redis Aiven provider (\#341)”; and 45 more (refs \#979, \#341, \#300, \#779, \#491, …).
lib/bolt/core/src/tasks/infra · medium confidence · unverified
5 commits (0 fixes) modifying engine/packages/auth-jwt
A change to existing behaviour in engine/packages/auth-jwt — 5 commits, 27 files: “update”; “feat(auth): add namespace-scoped JWT authentication (\#5780)” (refs \#5780).
engine/packages/auth-jwt · medium confidence · unverified
5 commits (0 fixes) modifying engine/packages/universalpubsub/src/pubsub/channel
A change to existing behaviour in engine/packages/universalpubsub/src/pubsub/channel — 5 commits, 5 files: “update”.
engine/packages/universalpubsub/src/pubsub/channel · medium confidence · unverified
5 commits (0 fixes) modifying engine/packages/util-id
A change to existing behaviour in engine/packages/util-id — 5 commits, 1 file: “update”; “feat(gas): implement smart pulling for horizontally scaled workers (\#3417)”; “chore: reorg in prep for merging rivetkit in to monorepo (\#3239)”; and 1 more (refs \#3417, \#3239, \#5780).
engine/packages/util-id · medium confidence · unverified
5 commits (0 fixes) modifying engine/sdks/rust/data/src/versioned/pegboard\_actor
A change to existing behaviour in engine/sdks/rust/data/src/versioned/pegboard\_actor — 5 commits, 12 files: “update”.
_engine/sdks/rust/data/src/versioned/pegboard\actor · medium confidence · unverified
5 commits (0 fixes) modifying lib/bolt/cli/src/commands/admin
A change to existing behaviour in lib/bolt/cli/src/commands/admin — 5 commits, 2 files: “Add admin login system”; “feat: Add cluster admin cli (\#644)”; “Add cli docs, add test”; and 2 more (refs \#644).
lib/bolt/cli/src/commands/admin · medium confidence · unverified
5 commits (0 fixes) modifying lib/bolt/core/src/dep/cloudflare
A change to existing behaviour in lib/bolt/core/src/dep/cloudflare — 5 commits, 2 files: “Remove Cloudflare tunnel”; “Allow configuring DNS without Cloudflare”; “Simplify domain”; and 2 more.
lib/bolt/core/src/dep/cloudflare · medium confidence · unverified
5 commits (1 fix) modifying infra/tf/grafana
A change to existing behaviour in infra/tf/grafana — 5 commits (1 fix), 5 files: “WIP grafana dashboard over cloudflare tunnel”; “fix(grafana): fix circular dependency between grafana \<-\> cockroachdb\_managed (\#760)”; “Format docume”; and 2 more (refs \#760, \#1216).
infra/tf/grafana · medium confidence · unverified
6 commits (0 fixes) modifying engine/packages/depot-client/src/filesystem
A change to existing behaviour in engine/packages/depot-client/src/filesystem — 6 commits, 15 files: “update”.
engine/packages/depot-client/src/filesystem · medium confidence · unverified
6 commits (0 fixes) modifying engine/packages/engine-context
A change to existing behaviour in engine/packages/engine-context — 6 commits, 16 files: “update”.
engine/packages/engine-context · medium confidence · unverified
6 commits (0 fixes) modifying engine/packages/keys
A change to existing behaviour in engine/packages/keys — 6 commits, 5 files: “update”.
engine/packages/keys · medium confidence · unverified
6 commits (1 fix) modifying infra/nix
A change to existing behaviour in infra/nix — 6 commits (1 fix), 6 files: “chore: remove unneeded nix configs (\#1248)”; “Update deps”; “fix: update rust nix pkg (\#648)”; and 3 more (refs \#1248, \#648, \#1216).
infra/nix · medium confidence · unverified
6 commits (1 fix) modifying lib/bolt/cli/src/commands/db
A change to existing behaviour in lib/bolt/cli/src/commands/db — 6 commits (1 fix), 2 files: “Add list migrations”; “chore: clippy fix pass (\#790)”; “chore: update bolt with new service definition (\#1211)”; and 3 more (refs \#790, \#1211, \#1209, \#1130).
lib/bolt/cli/src/commands/db · medium confidence · unverified
7 commits (0 fixes) modifying engine/packages/env
A change to existing behaviour in engine/packages/env — 7 commits, 29 files: “update”; “chore: clean up metrics (\#3660)”; “chore: reorg in prep for merging rivetkit in to monorepo (\#3239)” (refs \#3660, \#3239).
engine/packages/env · medium confidence · unverified
7 commits (0 fixes) modifying engine/packages/sqlite-embedded
A change to existing behaviour in engine/packages/sqlite-embedded — 7 commits, 11 files: “update”.
engine/packages/sqlite-embedded · medium confidence · unverified
7 commits (0 fixes) modifying engine/packages/state-machine-durable
A change to existing behaviour in engine/packages/state-machine-durable — 7 commits, 9 files: “update”.
engine/packages/state-machine-durable · medium confidence · unverified
7 commits (1 fix) modifying infra/salt/pillar
A change to existing behaviour in infra/salt/pillar — 7 commits (1 fix), 12 files: “Fix extra ATS secret”; “Remove salt from bolt & infra”; “Clean up Traefik service configs to allow for multiple Traefik services”; and 4 more.
infra/salt/pillar · medium confidence · unverified
7 commits (1 fix) modifying infra/tf/cloudflare\_tunnels
A change to existing behaviour in infra/tf/cloudflare\_tunnels — 7 commits (1 fix), 4 files: “WIP grafana dashboard over cloudflare tunnel”; “WIP get logs to grafana”; “Implement global sharding”; and 4 more (refs \#1216).
_infra/tf/cloudflare\tunnels · medium confidence · unverified
8 commits (0 fixes) modifying engine/packages/pegboard-envoy/src/sqlite
A change to existing behaviour in engine/packages/pegboard-envoy/src/sqlite — 8 commits, 5 files: “update”.
engine/packages/pegboard-envoy/src/sqlite · medium confidence · unverified
8 commits (0 fixes) modifying engine/sdks/schemas/data
A change to existing behaviour in engine/sdks/schemas/data — 8 commits, 52 files: “update”; “feat(auth): add namespace-scoped JWT authentication (\#5780)” (refs \#5780).
engine/sdks/schemas/data · medium confidence · unverified
8 commits (4 fixes) modifying rivetkit-typescript/packages/traces
A change to existing behaviour in rivetkit-typescript/packages/traces — 8 commits (4 fixs), 15 files: “chore: fmt”; “chore: fix remaining issues with rivetkit-core”; “fix(ci): stabilize pr actions (\#4381)”; and 5 more (refs \#4381, \#4120, \#4038, \#4280, \#4119, …).
rivetkit-typescript/packages/traces · medium confidence · unverified
9 commits (0 fixes) modifying infra/tf/nomad/files
A change to existing behaviour in infra/tf/nomad/files — 9 commits, 4 files: “Migrate imagor to k8s”; “Remove Imagor health check”; “Update Nomad deps”; and 5 more.
infra/tf/nomad/files · medium confidence · unverified
9 commits (2 fixes) modifying engine/sdks/rust/data
A change to existing behaviour in engine/sdks/rust/data — 9 commits (2 fixs), 2 files: “\[SLOP(claude-opus-4-8)\] feat: upstream OSS-safe engine + rivetkit changes from EE”; “update”; “chore: reorg in prep for merging rivetkit in to monorepo (\#3239)”; and 2 more (refs \#3239).
engine/sdks/rust/data · medium confidence · unverified
9 commits (3 fixes) modifying engine/packages/universalpubsub/src
A change to existing behaviour in engine/packages/universalpubsub/src — 9 commits (3 fixs), 3 files: “\[SLOP(claude-opus-4-8)\] feat: upstream OSS-safe engine + rivetkit changes from EE”; “update”; “fix(ups): formalize subjects (\#4334)”; and 4 more (refs \#4334, \#3239, \#3752, \#4368).
engine/packages/universalpubsub/src · medium confidence · unverified
Actor persistence schema upgraded to v4 with queue support and legacy data fixes
The actor-persist package now uses schema version 4, introducing a new QueueMessage type to support queue-based workflow runs and adding hibernatable WebSocket support in earlier versions. To ensure data integrity during this transition, the system now correctly handles legacy v4 actor schedules where arguments were stored as raw bytes instead of the expected CBOR format, preventing deserialization failures for actors persisted by a previous buggy writer. This change also includes a build script to compile BARE schemas and comprehensive tests to verify round-trip serialization and legacy fallback decoding.
rivetkit-rust/packages/actor-persist · high confidence
Engine configuration schema restructured with new security and runtime controls
The engine's configuration system has been reorganized into a modular schema, introducing several new capabilities and behavioral changes. Authentication now supports namespace-scoped JWTs by default, with an explicit \insecure\_allow\_unauthenticated\ flag to restore legacy unauthenticated access if needed. A new outbound request policy gates serverless runner HTTP calls behind an SSRF policy, allowing loopback by default but denying private networks and insecure schemes unless explicitly enabled. Runtime behavior includes a new \allow\_version\_rollback\ flag to control engine upgrades, configurable worker load-shedding curves, and a \force\_shutdown\_duration\ to prevent hanging processes. Additionally, SQLite depot configuration now exposes knobs to disable compaction and manage storage quotas, while the Guard service gains granular timeouts and rate-limiting controls for WebSocket and HTTP traffic. Also in this area: 1 commit (0 fixes) modifying (repo-wide); Code formatting applied to auth configuration tests.
engine/packages/config/src, engine/packages/config/src/config · low confidence · unverified
Envoy protocol SDK restructured with v8 types and streaming window configuration
The Rust Envoy protocol SDK has been reorganized to expose the latest protocol definitions (v8) as the default public API, replacing previous versioned exports. A new constant, HTTP\_STREAM\_INITIAL\_WINDOW\_BYTES, is now exposed to configure the initial unacknowledged body bytes allowed in HTTP stream directions, supporting end-to-end streaming behavior. Additionally, utility functions for generating random gateway and request IDs, along with ID-to-string conversion, have been added to the public interface.
engine/sdks/rust/envoy-protocol/src · high confidence
Envoy protocol schema advances to v8 with staged SQLite commits
The \engine/sdks/rust/envoy-protocol/schemas\ directory has been updated to include protocol definitions from v1 through v8. The most significant change is the introduction of staged commits in v8, which allows large SQLite updates to be written as a sequence of shard-aligned segments and finalized atomically, preventing partial visibility. This evolution also includes refinements to the SQLite error response structure (adding \group\ and \code\ fields) and adjustments to generation/transaction ID handling across versions. Also in this area: 2 commits (0 fixes) modifying (repo-wide).
engine/sdks/rust/envoy-protocol/schemas · medium confidence · unverified
Envoy protocol versioning scaffolding and compatibility checks
The \envoy-protocol\ crate now includes a \versioned\ module that manages protocol evolution from v1 through v8. This location provides the bidirectional conversion logic (e.g., \v1\_to\_v2.rs\, \v2\_to\_v3.rs\) and the central \ToEnvoy\ enum that handles serialization and deserialization across versions. It also introduces \ProtocolCompatibilityFeature\ and \ProtocolCompatibilityError\ to enforce version requirements for specific capabilities, such as SQLite startup data, page I/O, and remote execution.
engine/sdks/rust/envoy-protocol/src/versioned · high confidence
Epoxy protocol upgrades to v4 with backward-compatible versioned serialization
The Rust epoxy-protocol SDK now defaults to protocol v4, introducing a new build system that auto-generates types from schema files and exposes a \PROTOCOL\_VERSION\ constant. To ensure smooth migration, the library implements versioned serialization for core types (CommittedValue, CachedValue, AcceptedValue), allowing clients to encode and decode data in v2, v3, or v4 formats. Explicit converters handle field mapping between versions, and read-state operations now strictly require v4, while older v3 binaries can still read storage serialized in v3.
engine/sdks/rust/epoxy-protocol · high confidence
Examples updated to serverless format with explicit registry.start()
The example applications in examples/cross-actor-actions, examples/native-websockets, and examples/state have been migrated to a standardized serverless structure. This includes adding .gitignore files to exclude .actorcore, node\_modules, and public directories, and updating the backend entry points (src/index.ts) to explicitly call registry.start() to launch the server on port 6420. The examples now use a consistent Vite configuration with proxy settings for the actor server and include specific test configurations via vitest.config.ts.
examples/cross-actor-actions, examples/native-websockets, examples/state · high confidence
Introduces RAII-based gauge guards and standardized metric buckets
The metrics package now provides RAII-style gauge guards (IntGaugeGuard, FloatGaugeGuard) via the GaugeGuardExt trait, allowing users to automatically decrement gauges when a scope ends or a panic occurs, ensuring accurate tracking of in-progress work. Additionally, the package exposes standardized histogram bucket configurations (BUCKETS, MICRO\_BUCKETS, LIFETIME\_BUCKETS, PAGE\_COUNT\_BUCKETS, TASK\_POLL\_BUCKETS) and a centralized Prometheus registry, replacing previous ad-hoc metric definitions with a consistent, reusable library.
engine/packages/metrics · high confidence
Move lobby runtime aggregate logic into a dedicated query
The implementation of the lobby runtime aggregate operation has been refactored to move the core aggregation logic into a dedicated query. This change consolidates the data processing steps, ensuring that the aggregation of lobby durations and metadata is handled more efficiently within the query layer rather than in the application code.
svc/pkg/mm/ops/lobby-runtime-aggregate · medium confidence
New database key definitions for Pegboard actors, runners, and namespaces
The Pegboard engine now includes a comprehensive set of database key definitions in \engine/packages/pegboard/src/keys\ to manage internal state. This change introduces key structures for actors (including creation timestamps, workflow IDs, runner assignments, and connectivity flags), actor key-value stores (with support for exact and range queries), and runners (tracking creation, slots, and protocol versions). It also adds keys for namespace-level runner allocation indexes, runner configurations, and hibernating request tracking, establishing the data layout for these core engine components. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/pegboard/src/keys · low confidence · unverified
Pegboard engine restructured with SQLite v1-to-v2 migration and envoy expiration scheduler
The Pegboard engine source has been reorganized into a new modular structure, introducing a dedicated SQLite v1-to-v2 migration workflow that safely imports legacy actor databases into the new v2 storage format with crash-resilient checkpointing. Additionally, a new in-process Envoy expiration scheduler has been added to manage stale envoy cleanup with concurrency limits and deduplication, replacing the previous per-process spawning pattern. The update also includes comprehensive error definitions for actor and runner operations, new Prometheus metrics for tracking migration progress and envoy lifecycle, and pubsub subjects for runner and envoy routing. Also in this area: 1 commit (0 fixes) modifying (repo-wide).
engine/packages/pegboard/src · low confidence · unverified
Removal of legacy database operation implementations
This change removes the source code for multiple service operations (including CDN, Cloud, Game, Identity-Config, KV-Config, MM-Config, and User services) that previously handled database interactions via direct SQL queries. These files, which managed tasks such as namespace creation, version publishing, and token generation, have been deleted, indicating a migration away from the previous database access pattern in these specific service locations.
(repo-wide) · high confidence
Removal of legacy database query implementations
The direct SQL query implementations in the \game-user\, \mm\, \team-invite\, \token\, and \upload\ services have been removed. This cleanup eliminates the manual \sqlx\ query logic and row-mapping code that previously handled data retrieval for operations such as fetching game-user links, listing users, retrieving recent sessions, getting player details, fetching team invitations, validating tokens, and listing user uploads, indicating a shift away from these specific hand-written database access patterns.
(repo-wide) · high confidence
Removal of legacy database query operations
Deleted the implementation files for multiple service operations (including CDN namespace resolution, site retrieval, Cloud game configuration, Game listing and versioning, Matchmaker configuration, Team and User identity resolution, and Cloudflare custom hostname management). These operations previously executed direct SQL queries against their respective dedicated databases (such as db-cdn, db-game, db-cloud, db-mm-config, db-team, and db-user-identity) and are now removed, indicating a migration away from these standalone database access patterns.
(repo-wide) · high confidence
Removal of legacy key-value and search operation implementations
The codebase has removed the source files for several core operations, including \kv-get\, \kv-list\, \mm-lobby-history\, and \team-search\. These deletions indicate that the underlying logic for retrieving key-value pairs, listing KV entries, fetching lobby history, and searching teams has been replaced or migrated elsewhere, likely as part of the broader effort to migrate services to a single database and standardize query handling via macros.
(repo-wide) · medium confidence
Removal of namespaces and secrets documentation placeholders
The placeholder documentation files (.gitkeep and README.md) for the namespaces and secrets configuration directories have been removed. This eliminates the previous instructions for placing namespace and secrets configuration files as .toml files in these directories, indicating that this manual file-based configuration approach is no longer supported or documented in these locations.
namespaces, secrets · high confidence
Removal of team profile validation operation
The \team-profile-validate\ operation implementation has been removed from the codebase. This change eliminates the server-side logic that previously validated team display names (checking for length, format, and uniqueness) and biography fields (checking for length and format). Users relying on this specific validation step during profile updates will no longer have these checks performed by this operation.
svc/pkg/team/ops/profile-validate · high confidence
Removal of user-follow count and list operation implementations
The source files for the \user-follow-count\ and \user-follow-list\ operations have been deleted from the service. This removes the direct SQL query logic and response handling previously contained in these modules, indicating that the implementation for retrieving follow counts and listing follows has been moved or replaced elsewhere.
svc/pkg/user-follow/ops/count, svc/pkg/user-follow/ops/list · high confidence
Removal of user-follow relationship-get operation implementation
The implementation file for the user-follow-relationship-get operation has been deleted. This removes the logic that previously queried the database to determine follower/following status between user pairs and returned the mutual, follower, and following flags. This change is part of the broader migration to a single database and macro-based query structure.
svc/pkg/user-follow/ops/relationship-get · high confidence
RivetKit SDK breaking changes and self-hosted authentication requirements
The Rust SDK now supports actor action sets containing up to 128 action types (increased from 16). For self-hosted deployments, the engine now requires an admin token (\auth.admin\_token\) and Bearer token authentication; legacy unauthenticated access can be restored by setting \auth.insecure\_allow\_unauthenticated: true\. In the TypeScript SDK (\rivetkit\), \ctx.sql\ is removed in favor of \ctx.db\ from \rivetkit/db\, and concrete error classes like \QueueFull\ are replaced by the standardized \RivetError\ with \isRivetErrorCode\ checks. Several internal entrypoints (\rivetkit/driver-helpers\, \rivetkit/topologies\, \rivetkit/dynamic\, \rivetkit/sandbox\) are permanently removed, while \Registry.handler\ and \Registry.serve\ are restored for the native serverless runner.
(repo-wide) · high confidence
Fixes
7 commits (4 fixes) fixing infra/tf/cloudflare\_workers
A fix in infra/tf/cloudflare\_workers — 7 commits (4 fixs), 4 files: “Fix missing cf route”; “Fix cloudflare workers”; “Fix e2e init steps”; and 4 more (refs \#1216).
_infra/tf/cloudflare\workers · medium confidence · unverified
Introduce structured error handling with internal error exposure control
The engine now uses a new \RivetError\ system in \engine/packages/error/src\ that structures errors with groups, codes, and optional metadata, while introducing a mechanism to control the visibility of internal diagnostic details. Specifically, the \RivetError::build\_internal\ method now checks the \RIVET\_EXPOSE\_ERRORS\ environment variable; if set to \1\, internal error messages are exposed to the user, otherwise they are suppressed to prevent leaking sensitive implementation details. This change ensures that internal bridge errors are handled consistently and securely by default.
engine/packages/error · high confidence
Test coverage
13 commits adding/updating tests in lib/api-helper/build/tests; 4 commits adding/updating tests in infra/tests/stress-param; 6 commits adding/updating tests in infra/tests/standalone.
Dependencies
Introduce container-runner and engine package scaffolding
This change adds the \container-runner\ crate, a Rust serverless runner that hosts actors by spawning child game-server processes and proxying traffic, along with its associated e2e test examples. It also scaffolds a large number of new \engine/packages\ crates (including \api-builder\, \api-public\, \auth\, \bootstrap\, \cache\, \cli\, \config\, \depot-client\, \epoxy\, and \guard-core\), establishing the workspace structure and dependency definitions for the engine's modular architecture.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 46 → 53 (+6.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 63 → 61 (-2.0)
- Architecture 71 → 83 (+12.4)
- Maturity 83 → 82 (-0.3)
- Readiness 33 → 50 (+16.7)
- Security 48 → 42 (-6.0)
- Event Sourcing 100 → 100 (+0.0)
- Accessibility 61 → 73 (+12.1)
- Performance 69 → 85 (+16.4)
Resolved (1742)
- Change coupling: telemetry.rs ↔ telemetry.ts (rivetkit-rust/packages/rivetkit-core/src/telemetry.rs)
- ClassTooLong: DatabaseKv (engine/packages/gasoline/src/db/kv/mod.rs)
- ClassTooLong: InFlightRequestHandle (engine/packages/pegboard-gateway3/src/shared_state.rs)
- ClassTooLong: PegboardGateway (engine/packages/pegboard-gateway/src/lib.rs)
- ClassTooLong: PegboardGateway2 (engine/packages/pegboard-gateway2/src/lib.rs)
- ClassTooLong: PegboardGateway3 (engine/packages/pegboard-gateway3/src/lib.rs)
- ClassTooLong: ProxyService (engine/packages/guard-core/src/proxy_service.rs)
- ClassTooLong: Runner (engine/sdks/typescript/runner/src/mod.ts)
- ClassTooLong: Runner (rivetkit-typescript/packages/engine-runner/src/mod.ts)
- ClassTooLong: SubCommand (engine/packages/engine/src/commands/udb/cli.rs)
- ClassTooLong: Tunnel (engine/sdks/typescript/runner/src/tunnel.ts)
- ClassTooLong: Tunnel (rivetkit-typescript/packages/engine-runner/src/tunnel.ts)
- ClassTooLong: WorkflowCtx (engine/packages/gasoline/src/ctx/workflow.rs)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (frontend/package.json)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- …and 1722 more
New (1587)
- Acquire::run (cognitive 48) (engine/packages/pegboard-gateway/src/acquire.rs)
- Acquire::run (cyclomatic 33) (engine/packages/pegboard-gateway/src/acquire.rs)
- ActionDispatcher.make (cognitive 17) (rivetkit-typescript/packages/effect/src/internal/ActionDispatcher.ts)
- ActiveActorCountChanges::next (cognitive 25) (rivetkit-rust/packages/rivetkit-core/src/registry/serving_envoy.rs)
- ActorConnection.connectLoop (cognitive 17) (rivetkit-swift/Sources/RivetKitClient/ActorConnection.swift)
- ActorConnection.handleClose (cyclomatic 20) (rivetkit-swift/Sources/RivetKitClient/ActorConnection.swift)
- ActorHandle::handle_inbound (cognitive 19) (engine/packages/pegboard-envoy/src/connection.rs)
- ActorStateMachine::on_event (cognitive 174) (engine/packages/pegboard/src/actor_machine/mod.rs)
- ActorStateMachine::on_event (cyclomatic 157) (engine/packages/pegboard/src/actor_machine/mod.rs)
- ActorTask::handle_dispatch (cyclomatic 16) (rivetkit-rust/packages/rivetkit-core/src/actor/task.rs)
- ActorTask::start_actor (cognitive 30) (rivetkit-rust/packages/rivetkit-core/src/actor/task.rs)
- ActorTask::start_actor (cyclomatic 28) (rivetkit-rust/packages/rivetkit-core/src/actor/task.rs)
- Address::parse (cyclomatic 18) (engine/packages/api-peer/src/volumes/address.rs)
- AlarmManifestState::apply (cognitive 23) (engine/packages/depot-worker/src/tablet_coordinator_machine/state/alarms.rs)
- AlarmManifestState::apply (cyclomatic 17) (engine/packages/depot-worker/src/tablet_coordinator_machine/state/alarms.rs)
- Balancing::status (cognitive 16) (engine/packages/depot-worker/src/tablet_coordinator_machine/state/balancing.rs)
- Cache::ring (cognitive 26) (engine/packages/auth-jwt/src/runtime.rs)
- Cache::ring (cyclomatic 16) (engine/packages/auth-jwt/src/runtime.rs)
- Chain::from_pages (cognitive 18) (engine/packages/sqlite-prefetch/src/overflow/chain.rs)
- ClaimSnapshot::chunks (cognitive 17) (engine/packages/depot-client/src/filesystem/remote.rs)
- …and 1567 more
Changes since last survey
- 68 commits — 64 feature/other, 4 fixes
By area
- rivetkit-typescript/packages — 17 commits
- engine/packages — 12 commits
- docs/actors — 7 commits
- rivetkit-rust/engine — 6 commits
- engine/sdks — 5 commits
- (root) — 4 commits
- docs/general — 3 commits
- examples/docs — 3 commits
- rivetkit-rust/packages — 3 commits
- docs/api — 2 commits
- (repo) — 1 commit
- .github/workflows — 1 commit
- docs/durable-streams — 1 commit
- engine/artifacts — 1 commit
- examples/hello-world-render — 1 commit
- examples/turso — 1 commit
Notable commits
- fix: fix(depot-client): invalidate stale read caches after page commits
- fix: fix(envoy-client): drop trailing frames for completed HTTP requests
- fix: fix(envoy-client): mint a new envoy key after the lost threshold stops all actors (#5913)
- fix: fix(sqlite): classify operation error logs
- change: chore(logging): reduce expected runtime error noise
- change: chore(release): omit temporary generated error artifacts
- change: chore(release): update version to 2.3.31
- change: chore(release): update version to 3.0.0-preview.3
- change: chore(release): update version to 3.0.0-preview.4
- change: chore(release): update version to 3.0.0-preview.5
- change: chore(release): update version to 3.0.1
- change: chore(release): update version to 3.0.1-preview.2
- change: chore(release): update version to 3.0.2
- change: chore(release): update version to 3.0.3
- change: chore(release): update version to 3.0.4
- change: chore(release): update version to 3.0.5
- change: chore(release): update version to 3.0.6
- change: chore(release): update version to 3.0.7
- change: chore(release): update version to 3.1.0
- change: chore(release): update version to 3.1.0-rc.1
- …and 48 more
Architecture
- Containers 0 added · 0 removed · contexts 0 added · 1 removed · edges 0 added · 0 removed
Removed bounded contexts (1)
- sdk
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
rivet-dev/actors was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 319e4d2940089bc6db42d2f99c6d83dcd33aaa3a — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-e1a3b69fc8ee.