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

Service	Status	Web	Updated (UTC)
frontend-inspector	❌ Build Failed (View Logs)	Web	Mar 25, 2026 at 7:58 pm
kitchen-sink	❌ Build Failed (View Logs)	Web	Mar 25, 2026 at 7:58 pm
frontend-cloud	🕒 Building (View Logs)	Web	Mar 25, 2026 at 7:58 pm
website	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am
mcp-hub	✅ Success (View Logs)	Web	Mar 24, 2026 at 3:29 am
ladle	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am

• fix(rivetkit): copy Buffer to Uint8Array in ensureUint8Array to fix .slice() semantics #4506 : 2 dependent PRs (#4502 , #4510 )
• fix(rivetkit): setup database before lifecycle hooks for c.db availability #4494
• fix(rivetkit): remove drizzle-orm peer dep and add runtime version check #4492 👈 (View in Graphite)
• chore(skill): add version check to rivetkit skill #4491
• fix(rivetkit): prevent Turbopack from tracing sqlite-vfs dynamic import #4490
• fix(rivetkit): warn when manager port falls back to a different port #4489
• fix(rivetkit): clear connectableTs on actor sleep #4488
• fix(rivetkit): gate node:sqlite behind RIVETKIT_NODE_SQLITE env var #4487
• main

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

PR Review: fix(rivetkit): remove drizzle-orm peer dep and add runtime version check

Overall this is a clean, focused change. The approach of removing the peer dep and adding a runtime warning is a good pattern for handling version compatibility. A few observations:

Correctness

test-drizzle-compat.sh - missing final newline in results table. The summary loop at the end has no trailing echo after the loop, so the last result line may get concatenated with the shell prompt in some terminals. Minor, but easy to fix by adding a closing echo after the for loop.

test-drizzle-compat.sh - set -e + cleanup trap interaction. The script uses set -euo pipefail. If pnpm install inside cleanup() fails on restore (e.g., network issue), the trap exits with an error and the calling process may see a misleading exit code. Consider adding || true to the restore pnpm install call - the goal of cleanup is best-effort restoration, not failure propagation.

Version check - createRequire is Node-specific. The node:module import works fine for Node.js but will throw in edge runtimes (Cloudflare Workers, Deno, Bun with strict mode, etc.). The try/catch already handles this gracefully, but a comment explaining why the catch is silent would help future maintainers understand it is intentional.

Design

DRIZZLE_MAX is exclusive but the constant name does not make that clear. The comment helps, but renaming to DRIZZLE_MAX_EXCLUSIVE or DRIZZLE_UPPER_BOUND would self-document the intent and prevent an off-by-one if someone edits the bounds later.

Module-level drizzleVersionChecked flag. Fine for typical usage, but because the flag is module-level it persists across tests in the same Node.js process. If a test wants to verify the warning fires, it will not unless the flag is reset. Not a blocker, just worth noting.

Style and Conventions

• compareVersions is straightforward and readable.
• Removing drizzle-orm from peerDependencies while keeping drizzle-kit is consistent - drizzle-kit is a build/migration-time tool, so keeping it as a peer dep makes sense.
• The CLAUDE.md update is clear and useful for maintainers.
• The formatting-only change to runInlineMigrations is fine.
• The warning message correctly points to github.com/rivet-dev/rivet/issues per repo conventions.

Summary: The set -e/cleanup interaction in the shell script is the only item worth addressing before merge; the rest are low-priority suggestions.

Merge activity

• Mar 25, 7:43 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 25, 7:58 PM UTC: Graphite rebased this pull request as part of a merge.
• Mar 25, 7:59 PM UTC: @NathanFlurry merged this pull request with Graphite.