chore(release): staging to production - 2026.06.03 - #1091
Merged
Conversation
…1090) ## Summary - `MainLayout`'s main content area offset itself by `drawerWidth` (260px) whenever the menu state was "closed" (the default below the `lg` breakpoint), via `margin-left: -260px` and `width: calc(100% - 260px)`. - The in-layout `<Sidebar />` drawer it was compensating for is commented out (the studio renders its own `AppDrawer`), so this offset was phantom: it shifted content off-screen and shrank its width by 260px, breaking responsiveness on sub-`lg` widths. - The `!open` branch now uses `margin-left: 0`, `width: 100%`, keeping only the responsive `padding`. Removed the now-unused `drawerWidth` import. This is the permanent equivalent of "unchecking" `margin-left: -260px` (and reclaiming the lost 260px of width) that was confirmed to fix the layout in devtools. ## Test plan - [ ] Load a `sidekick-studio` page (e.g. `/sidekick-studio/admin/guardrails`) - [ ] Resize the viewport below ~1200px (lg) and confirm content is no longer shifted off-screen or horizontally overflowing - [ ] Confirm layout is unchanged at >= lg widths
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
## Summary - Harden the shared axios response interceptor in `packages/ui/src/api/client.js` to use optional chaining (`error.response?.status`) instead of `error.response.status`. - On network failures, CORS-blocked responses, and gateway timeouts (e.g. a `504 Gateway Timeout` returned by the ALB with no `Access-Control-Allow-Origin` header), `error.response` is `undefined`. The previous code threw `Cannot read properties of undefined (reading 'status')`, which aborted the interceptor and masked the real failure across the whole app. - With this guard, such errors now fall through to the existing `return Promise.reject(error)`, so callers' `.catch` handlers run and the actual error message surfaces. ### Context Surfaced while diagnosing the Guardrails Settings page: `GET /api/v1/guardrails/selftest` was returning a `504` (backend can't reach the Fiddler VPC endpoint outside the VPN), and the resulting CORS/`ERR_FAILED` rejection had no `error.response`, triggering the `reading 'status'` crash shown in the Plan capabilities panel. This change does not fix the underlying Fiddler reachability (infra/VPC endpoint work); it only makes the client fail gracefully. ### Risk Behavior is unchanged for any real HTTP response (including the 401 / token-refresh flow, which still has `error.response`). The optional chaining only adds graceful handling for the previously-crashing no-response case. ## Test plan - [ ] Trigger an API call that fails with no response (e.g. network offline / 504 from gateway) and confirm the UI shows a real error instead of `Cannot read properties of undefined (reading 'status')`. - [ ] Confirm a genuine 401 still triggers token refresh / redirect to login as before.
maxtechera
temporarily deployed
to
staging - aai-unified2-flowise-moonstruck
June 3, 2026 19:43 — with 
Render
Inactive
Render
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Release: Staging to Production
Release Date: 2026-06-03
Changes in this release
This PR is automatically created/updated when commits are pushed to staging.
Merging this PR will trigger the release workflow to create a new GitHub release.