fix: deploy quick fixes

[ogzhanolguncu]

What does this PR do?

This PR fixes:

• Safari network tab rendering issue

• Locks network tab to eliminate weird panning issues
• Fixes hover issue of workplace switcher

• Makes sure when reading the RPS for sentinel we read the correct project's sentinel
• Uses same default value for items in the /project/settings
• Removes faulty default value for healthcheck setting

- Removes `Environment Variables` and `Custom Domains` from project overview coz they are moved to settings.

How should this be tested?

• Just trigger a deployment locally and check network tab
• Play around with the UI a bit

Checklist

Required

• Filled out the "How to test" section in this PR
• Read Contributing Guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Ran make fmt on /go directory
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Unkey Docs if changes were necessary

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready	Preview, Comment	Feb 23, 2026 11:59am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
engineering	Ignored	Preview	Feb 23, 2026 11:59am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6416654 and 72e9bb4.

📒 Files selected for processing (1)

• web/apps/dashboard/app/(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/deployment-network-view.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

• web/apps/dashboard/app/(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/deployment-network-view.tsx

---

📝 Walkthrough

Walkthrough

This pull request updates the deployment network visualization with a locked canvas state, refactors node styling and health indicator layouts, renames the network generation model from regions to sentinels, modifies settings forms to remove empty-state labels, and adds Safari-specific CSS fixes for foreignObject rendering.

Changes

Cohort / File(s)	Summary
Infinite Canvas Locked State deployment-network-view.tsx, infinite-canvas.tsx	Adds locked prop to InfiniteCanvas, disabling all mouse/wheel interactions and zoom momentum when activated. Adjusts canvas origin and spacing configuration.
Tree Node Sizing & Rendering tree-element-node.tsx, tree-layout.tsx, canvas-boundary.tsx	Introduces size prop to TreeElementNode for explicit width/height specification. Updates tree rendering to pass node dimensions and Safari-specific fix flag for foreignObject compatibility.
Node Layout & Health Indicators node-wrapper.tsx, health-banner.tsx, status-dot.tsx, status-indicator.tsx, skeleton-node.tsx, skeleton-layout.tsx	Refactors node styling by removing relative positioning, simplifying hover effects, and converting gradient layouts to CSS grid. Updates status indicators with grid-based positioning and removes variant prop. Removes skeleton node entries and simplifies status indicator placeholders.
Live Indicator live.tsx	Removes variant prop from StatusDot component call, relying on default behavior.
Network Generation Schema Refactor tree-generate.tsx, generate.ts, get-sentinel-rps.ts	Renames deployment network configuration from regions/instancesPerRegion to sentinels/instancesPerSentinel. Updates presets, health distributions, and sentinel selection logic. Adds projectId filtering for sentinel lookups. Introduces mapRegionToFlag utility for flag code generation.
Settings Forms Empty State Handling command.tsx, custom-domains/index.tsx, env-vars/index.tsx, regions.tsx, healthcheck/index.tsx, form-setting-card.tsx	Removes "None" or default labels from settings cards when no data is present. FormSettingCard adds nullish coalescing fallback to conditionally display "None" label. Healthcheck component refactored with hasPreviousData flag.
Project Page & Navigation [projectId]/page.tsx, team-switcher.tsx	Removes Custom Domains and Environment Variables sections from project page. Adds hover background styling to workspace switcher menu items.
CSS & Animation Updates tailwind.css, tailwind.config.js	Adds Safari-specific .safari-fo-fix CSS workaround for foreignObject rendering with animation adjustments. Changes marquee animation from transform-based to text-indent-based.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 10.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'fix: deploy quick fixes' is vague and uses generic terminology like 'quick fixes' that doesn't convey the specific changes made.	Consider using a more specific title that highlights the main fix, such as 'fix: Safari network tab rendering and deployment settings issues' or 'fix: multiple deployment UI and settings fixes'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description lists the fixes being addressed and provides testing instructions, but the required checklist items are not marked complete, indicating incomplete preparation for review.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch deploy-quick-fixes

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

web/apps/dashboard/app/(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/unkey-flow/components/simulate/tree-generate.tsx (1)

224-258: ⚠️ Potential issue | 🟡 Minor

Set min="1" for instance sliders to prevent empty sentinel groups.

The slider currently allows 0 instances per sentinel, which would create sentinels with no children in the visualization. While this doesn't cause a divide-by-zero error (the generator uses Array.from({ length: instanceCount }, ...) which handles 0 gracefully), it produces semantically invalid network topologies. All preset configurations enforce min >= 1, so the slider should do the same.

Fix

-                min="0"
+                min="1"
...
-                min="0"
+                min="1"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@web/apps/dashboard/app/`(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/unkey-flow/components/simulate/tree-generate.tsx
around lines 224 - 258, The instance-per-sentinel range inputs allow 0
currently; change both input elements that read/write
customConfig.instancesPerSentinel (the two <input type="range"> controls whose
onChange call setCustomConfig) to use min="1" instead of min="0" so sliders
cannot select zero, and ensure the onChange handlers clamp/adjust the paired
value if necessary to keep min <= max (update setCustomConfig logic in those
handlers to enforce the constraint while preserving generateMutation.isLoading
disabling).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@web/apps/dashboard/app/`(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/unkey-flow/components/nodes/node-wrapper/health-banner.tsx:
- Line 20: Replace the Tailwind template literal width class which the JIT can't
detect by moving the dynamic width into an inline style: keep the static
Tailwind classes (e.g., "mx-auto" and "-m-[20px]") on the div in the
HealthBanner component and add a style prop that sets width using
DEFAULT_NODE_WIDTH (e.g., style={{ width: `${DEFAULT_NODE_WIDTH}px` }} or
equivalent), removing the `w-[${DEFAULT_NODE_WIDTH}px]` from the className.

In
`@web/apps/dashboard/app/`(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/unkey-flow/components/tree/tree-element-node.tsx:
- Around line 1-35: The TreeElementNode component signature now requires a size
prop but canvas-boundary.tsx's error boundary fallback (the <TreeElementNode> at
line 11) is missing it; update that TreeElementNode usage to include a size
object (e.g., width: 400, height: 250) along with the existing id and position
so it matches how tree-layout.tsx passes size (NODE_SIZES[...] ) and preserves
the doubling logic in TreeElementNode.

In `@web/apps/dashboard/lib/trpc/routers/deploy/network/generate.ts`:
- Around line 14-19: The schema allows instancesPerSentinel.min >
instancesPerSentinel.max which can produce a negative range for getRandomInt;
update generatorConfigSchema to add a cross-field validation (using z.refine or
superRefine) on the instancesPerSentinel object to ensure min <= max and return
a clear validation error message; reference the instancesPerSentinel object and
its min/max fields in the refinement so the constraint is enforced before any
code (e.g., where getRandomInt is used) runs.

---

Outside diff comments:
In
`@web/apps/dashboard/app/`(app)/[workspaceSlug]/projects/[projectId]/(overview)/deployments/[deploymentId]/network/unkey-flow/components/simulate/tree-generate.tsx:
- Around line 224-258: The instance-per-sentinel range inputs allow 0 currently;
change both input elements that read/write customConfig.instancesPerSentinel
(the two <input type="range"> controls whose onChange call setCustomConfig) to
use min="1" instead of min="0" so sliders cannot select zero, and ensure the
onChange handlers clamp/adjust the paired value if necessary to keep min <= max
(update setCustomConfig logic in those handlers to enforce the constraint while
preserving generateMutation.isLoading disabling).