main=990f31cac2567163a15c7fa603abfebe5bdcdb9e pr_head=588ed2506a95b394f6825ec92b8aa826da6c30c2 merge_base=63bf014dc3fb35e76c32d4ca23ed0485cd5d47f7 PASS #38839 is on main as 528687d226 (fix(acp-registry): inherited NPM_CONFIG_PREFIX no longer overrides the managed npm prefix on Windows (#38839)) PASS gh: #38839 is MERGED with merge commit 528687d226 PASS the PR's merge-base 63bf014dc3 already contains #38839 PASS git diff merge-base..PR head is empty: the PR changes no files PASS merging the PR head into main yields main's tree unchanged Tests 1 passed | 41 skipped (42) PASS at 528687d226, a win32 npx install with an inherited NPM_CONFIG_PREFIX gives npm only the managed npm_config_prefix Tests 1 passed | 42 skipped (43) PASS on main 990f31cac2, the same test passes ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯ Tests 1 failed | 41 skipped (42) [07:38:08.946] ERROR (#1): Error [AssertionError]: expected [ 'NPM_CONFIG_PREFIX', …(1) ] to deeply equal [ 'npm_config_prefix' ] AssertionError: expected [ 'NPM_CONFIG_PREFIX', …(1) ] to deeply equal [ 'npm_config_prefix' ] PASS at the fix's parent 528687d226^, the same test fails: npm receives both prefix spellings VERDICT: CLOSE (already-fixed) - #38839 fixed issue #38697 and this PR's head no longer changes anything