[codex] Finish sandbox demo UX and flows#60
Merged
renanmpimentel merged 1 commit intomainfrom Apr 22, 2026
Merged
Conversation
Contributor
WalkthroughO pull request atualiza versões de ações do GitHub em quatro workflows (CI, deploy-prod, deploy-sandbox, pr-review) e refatora componentes de layout para converter sidebars de posicionamento Changes
Estimated code review effort🎯 2 (Simples) | ⏱️ ~12 minutos 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/ci.yml:
- Line 17: You updated uses: actions/setup-node@v5 which has breaking changes;
update the workflow to explicitly disable the new automatic cache (add
package-manager-cache: false under the setup-node step if you don't want
automatic caching based on package.json's packageManager field), and explicitly
set node-version (e.g., node-version: '20' or bump your runners to v2.327.1+ and
accept Node 24) to control the runtime; also audit downstream action upgrades
(e.g., actions/checkout v5) mentioned in the note and adjust the workflow
accordingly.
In @.github/workflows/deploy-prod.yml:
- Line 93: The workflow change to uses: actions/checkout@v5 upgrades the action
runtime to Node.js 24 and requires GitHub Actions runner version v2.327.1 or
newer; before switching to actions/checkout@v5, verify your runners meet or
exceed v2.327.1 (especially any self-hosted runners) and either update those
runners to v2.327.1+ or keep using actions/checkout@v4 (or pin a compatible
checkout action) until the runners are upgraded; also review any custom steps or
toolchains that assume Node.js 20 and update them to be compatible with Node.js
24 if you proceed with v5.
- Around line 96-99: Update the workflow to ensure the runners meet the Node.js
24 requirement for docker/setup-buildx-action@v4 and docker/login-action@v4:
verify or pin the GitHub Actions runner version to v2.327.1+ (or ensure
self-hosted runners have Node.js 24), and if runners cannot be guaranteed,
either revert to a v3 tag of these actions or add an explicit check/step that
validates runner Node.js version before using setup-buildx-action@v4 and
login-action@v4; reference the action identifiers docker/setup-buildx-action@v4
and docker/login-action@v4 when making the change.
In @.github/workflows/deploy-sandbox.yml:
- Line 55: Replace or gate the new checkout action usage: either revert to the
previous stable 'uses: actions/checkout@v4' or, if you intend to use 'uses:
actions/checkout@v5', add an explicit compatibility check and documentation that
all runners are upgraded to GitHub Actions runner >= v2.327.1; update the
workflow (where 'uses: actions/checkout@v5' appears) and the deployment
docs/README/CI runbook to assert runner versions and/or add a conditional step
that verifies runner version before proceeding with deploy.
- Around line 58-61: Confirmar compatibilidade do runner garantindo que o
ambiente CI use GitHub Actions Runner v2.327.1+ antes de manter `uses:
docker/setup-buildx-action@v4` e `uses: docker/login-action@v4`;
alternativamente, pinear para uma major anterior (ex.: `@v3`) ou adicionar uma
verificação de versão no workflow antes desses passos; localizar as entradas
`docker/setup-buildx-action@v4` e `docker/login-action@v4` no workflow e
atualizar para uma das opções: (1) documentar/exigir runner >= v2.327.1 no
README/CI, (2) change to stable v3 pins, or (3) insert a runtime check step that
fails with a clear message if runner < v2.327.1.
In @.github/workflows/pr-review.yml:
- Line 24: The workflow currently uses actions/setup-node@v5 which introduces
breaking changes (auto cache when packageManager exists, defaults to Node.js 24,
and requires runner v2.327.1+); update the workflow by either pinning setup-node
to a v4 release (e.g., actions/setup-node@v4) or explicitly configuring
v5-compatible settings: set package-manager-cache: false if you need to disable
automatic caching, explicitly set node-version to the desired Node.js (e.g., 20)
instead of relying on defaults, and ensure your runners meet the minimum version
(v2.327.1+) before merging; check for any cache or dependency behavior changes
caused by packageManager presence in package.json and validate CI runners and
jobs referencing actions/setup-node@v5 accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1028b71c-5aec-4766-b578-983f3b996125
📒 Files selected for processing (8)
.github/workflows/ci.yml.github/workflows/deploy-prod.yml.github/workflows/deploy-sandbox.yml.github/workflows/pr-review.ymlsrc/app/components/layout/InstitutionLayout.tsxsrc/app/components/layout/PatientLayout.tsxsrc/app/components/layout/SandboxShellLayouts.test.tsxsrc/app/components/layout/SupporterLayout.tsx
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
1 participant
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.
What changed
sessionStoragefor privacy, security, and history stateWhy
The sandbox still felt partially mocked: the copy was too technical, several profile actions were dead ends, dream lists grew without pagination, chats did not demonstrate moderation clearly, and persona fixtures were too sparse to support a convincing demo.
This branch closes that gap while also preserving the earlier shell scroll fix and the Node 24 workflow update already published in this PR.
Impact
/dreams/mine?page=...pagination, functional profile sections, and moderated chat behaviorValidation
npm run lintnpm run typechecknpm run test