fix: stabilize OAuth tests and Windows npm staging - #46545
Open
rekram1-node wants to merge 5 commits into
Open
Conversation
This was referenced Sep 1, 2026
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.
Summary
Keep the confirmed, limited CI fixes without expanding into Windows junction repair.
The later Windows junction-repair change has been reverted. No test skips, mutation retries, permission-policy changes, dependency changes, or schema-comment changes.
Validation
Bun 1.4.0 on macOS, for the retained changes:
Remaining Failures
The retained changes passed the Windows server suite and resolved the npm EPERM rename and tar-path errors. Two Windows Git dependency tests still fail because directory links point at the old staging location. Those are intentionally deferred.
The last run of the retained code also reported a Linux module-resolution error in the unchanged tool-edit test; that test and the full core suite pass locally. This PR does not claim all CI checks are green.