Remove VSCode 1.129.1 pin — regression fixed in 1.131.0 - #11440
Draft
timotheeguerin with Copilot wants to merge 2 commits into
Draft
Remove VSCode 1.129.1 pin — regression fixed in 1.131.0#11440timotheeguerin with Copilot wants to merge 2 commits into
timotheeguerin with Copilot wants to merge 2 commits into
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
microsoft-github-policy-service
Bot
added
the
ide
Copilot
AI
changed the title
[WIP] Investigate VSCode e2e test timeout issue
Remove VSCode 1.129.1 pin — regression fixed in 1.131.0
Jul 29, 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.
VSCode 1.130.0 introduced a regression causing e2e tests to hang indefinitely in CI. Tests were temporarily pinned to 1.129.1. VSCode 1.131.0 (released July 29, 2026) resolves the regression.
Changes
download-setup.ts— RemoveVSCODE_PINNED_VERSION = "1.129.1"constant;download()now defaults to latest stablepackage.json— Remove hardcoded--commit=8a7abeba...fromtest:webscript; tests run against latest stable