fix(frontend): remove flashing upgrade notice

[jog1t]

Description

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

Type of change

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

How Has This Been Tested?

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

Checklist:

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

[railway-app]

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

Service	Status	Web	Updated (UTC)
frontend-cloud	😴 Sleeping (View Logs)	Web	Mar 19, 2026 at 9:06 am
frontend-inspector	😴 Sleeping (View Logs)	Web	Mar 18, 2026 at 9:31 pm
ladle	❌ Build Failed (View Logs)	Web	Mar 18, 2026 at 9:22 pm
website	❌ Build Failed (View Logs)	Web	Mar 17, 2026 at 11:11 pm
mcp-hub	✅ Success (View Logs)	Web	Mar 17, 2026 at 11:09 pm

[jog1t]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(frontend): remove flashing upgrade notice #4451 👈 (View in Graphite)
• fix(frotnend): fix icons kiling the bundle #4450
• feat(frontend): ping actor if its in the crash loop #4448
• fix(engine): use proper paths for settings #4447
• feat(frontend): add outdated indicator to runners #4446
• main

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

[claude]

Code Review. PR: fix(frontend): remove flashing upgrade notice. File: frontend/src/components/actors/guard-connectable-inspector.tsx. Summary: Minimal, focused fix that corrects a subtle UX bug in the InspectorGuard component. Reorders two conditional checks to prevent an unintended flash of the upgrade notice during the initial query loading phase. Analysis - Root cause: The original guard evaluated the not-data/error/not-isInspectorAvailable check before the isLoading check. On first render, data is undefined while the query is in-flight, so the first branch fires immediately showing the upgrade banner before the query completes -- even for fully supported actors. The fix: Correct order after the patch checks isPending first (show ConnectingInspector during the initial fetch), then checks !data/error/!isInspectorAvailable (show OutdatedInspector only after the query settles). isLoading to isPending change: Semantically correct for TanStack Query v5. isLoading is isFetching && isPending, which can be false during a background refetch on stale data. isPending is true only when no cached data exists yet. Verdict: The fix is correct, minimal, and well-scoped. No concerns with code quality, security, or performance.

[pkg-pr-new]

More templates

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

@rivetkit/cloudflare-workers

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/sqlite-vfs

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

@rivetkit/traces

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

@rivetkit/workflow-engine

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

@rivetkit/virtual-websocket

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

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: e83b68b