[rahultee]

Why

The default Node override changed a build-only dependency of .NET 9/10. This invalidated cached SDKs and exposed a .NET 10 source-build failure.

What changed

Keep dotnetCorePackages in the original package set. All .NET SDK inputs and versions match the baseline before the Node override. Patched Node and selected-runtime tool bindings remain unchanged.

The older Node dependency is build-only: the restored .NET 10 SDK runtime closure contains no Node package. This change avoids the new source build; it does not fix or diagnose its inner compiler error.

Test plan

• scripts/ci_check.sh passed.
• .NET 8/9/10 development and deployment module derivations match the baseline before the Node override.
• The full .NET 10 deployment dependency graph matches the baseline exactly (811 derivations).
• .NET 10 development/deployment modules built successfully using the cached SDK. A local console project restored without a remote package source and printed Hello, World!.
• OCI and production disk dependency graphs select the baseline .NET bootstrap derivation, not the failed replacement.
• Compared all 106 development module derivations: only .NET 9/10 changed. No Node toolchain fixes were reverted.
• Full OCI images and production disks were not built or deployed.

Rollout

Merge through the normal release process, then build the new revision. No production rerun or deployment was performed.

• This is fully backward and forward compatible

~ written by ⠕ Replit

[rahultee]

@vlinkz it seems like dotnet has a dev dependency on node 🫠