<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions --> <!-- 🔎 Search existing issues to avoid creating duplicates. --> <!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ --> <!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --> <!-- 🔧 Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes <!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --> <!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. --> Version: 1.102.0 (user setup) Commit: cb0c47c0cfaad0757385834bd89d410c78a856c0 Date: 2025-07-09T22:10:34.600Z Electron: 35.6.0 ElectronBuildId: 11847422 Chromium: 134.0.6998.205 Node.js: 22.15.1 V8: 13.4.114.21-electron.0 OS: Windows_NT x64 10.0.19045 (new to dev containers so sorry if I'm just missing something obvious but) Steps to Reproduce: 1. Clone this repo 2. Open dev container via VS Code's built in recommendation 3. Container fails to start, with error `Please use Node.js v22.15.1 or later for development.` (looks like this has been broken for 3 weeks due to https://github.com/microsoft/vscode/commit/eee3294912305416c8d27c8ec26f483e7c529538#diff-a87e42db9496a50d2275b352cbf6750c999b679b9a70e109346af0ef01b32c16R13 ?)