On Windows, differently-cased environment variable names can no longer override ones the host has claimed.
What's wrong with this entry?
Environment variables claimed by the host can no longer be overridden by a differently-cased key, which mattered on Windows where env var names are case-insensitive.
- The claimed set is built by uppercasing the keys of
process.env. - The filter that strips settings-provided env compares with
.toUpperCase(). - The guard that drops lower-trust redirects does the same.
if (!uhr.has(r.toUpperCase())) t[r] = n;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window