Repository navigation
Conversation
8 of 9 tasks
Reapply the Node 24 server and host-runtime policy from #26171 after its temporary compatibility rollback. Keep this change in a draft PR until host compatibility, fallback behavior and rollout communication have been reviewed so existing users are not unexpectedly forced to upgrade.
nwparker
force-pushed
the
nwparker/restore-node24-after-rollout-validation
branch
from
October 9, 2026 09:01
c8778a5 to
f2c6e0f
Compare
nwparker
changed the base branch from
nwparker/temporary-node24-rollback
to
main
October 9, 2026 09:01
7 tasks done
This branch has not been deployed
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
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.
ELI5
Preserve the Node 24 transition as a draft while the temporary rollback protects existing SSH and WSL users from a surprise runtime requirement.
What Changed
Reapplies #26171 after the temporary rollback: servers and selected host runtimes require Node 24, companion builds target Node 24, and CI, tests and installation guidance follow that baseline. The compatibility launcher continues to run on older host Node and start Orca's bundled runtime. The bundled Node 24 runtime remains the default.
Why
A consistent Node 24 baseline remains the intended direction. The change was temporarily rolled back to avoid near-term user disruption while the host compatibility and rollout expectations are reviewed. Keeping the complete change in a draft makes it easy to resume without losing the prior work or prematurely raising the requirement again.
Linked Issue
N/A — maintainer-requested follow-up to the temporary rollback in #26823, restoring #26171.
Visual Proof
N/A — runtime compatibility and build policy; no UI layout or interaction changes.
Testing
Restores the runtime, host-discovery and CI-policy tests from #26171. The restoration tree exactly matches main before the rollback. Fresh checks must pass before this draft is marked ready.
Before marking ready:
Review
Draft intentionally held for compatibility and rollout review. This PR is not approved for immediate merge.
Agent skill upstream boundary
Notes
Based on main after merged rollback #26823. The complete restoration is reviewable here and remains a draft until rollout validation is complete. No remote wire or persistence format changes.
Checklist
N/Awith reasonpnpm lint,pnpm typecheck,pnpm test, andpnpm buildpass (or CI will cover; local preferred)