fix(sandbox): upgrade Node runtime to 24.18.0 - #83
Merged
Conversation
iamjr15
added a commit
that referenced
this pull request
Jul 27, 2026
## Decision Promote the immutable Daytona snapshot built from main at `b0d3572dc6d5bb199c2f7128da3e0eb4cb72e2a0`. ## Why The prior Node 22 snapshot can hit mounted-volume timestamp failures during dependency recovery. The replacement uses Node 24.18.0 and includes the reviewed bundled-dependency security patches from #83 and #84. ## Evidence - Protected snapshot run: https://github.com/cheatcode-ai/cheatcode/actions/runs/30268573116 - Published active snapshot: `cheatcode-sandbox-viewer-bundle-b0d3572dc6d5-30268573116` - Image vulnerability, secret, and configuration scans passed - Runtime smoke checks passed, including exact Node/NSS/embedded-package versions and all bundled tools, templates, and skills - Agent-worker lint, typecheck, and production dry-run build pass locally under Node 24.18.0 ## Scope One reviewed configuration change only. No schema or migration changes.
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.
Summary
Context
Production upload QA proved that files persist under the project
uploadsdirectory, remain available through the slash picker in later chats, and are readable by the agent. Recovery of one pre-existing mobile workspace still failed because Node 22.22.2/libuv treats timestamp preservation on the Daytona-mounted workspace as fatal, causing pnpm to exit withEPERM: operation not permitted, futime.Node 24.18.0 contains the upstream mounted-filesystem copy fix and is compatible with the pinned npm 12.0.1 and pnpm 11.15.0 toolchain. This changes the runtime baseline directly; it does not add a package-manager workaround or legacy path.
Decisions
Verification
No database migration or data mutation is included. No Linear issue or plan document is associated with this production QA fix.