Bump @vscode/test-electron from 2.5.2 to 3.1.0

[dependabot]

Bumps @vscode/test-electron from 2.5.2 to 3.1.0.

Changelog

Sourced from @​vscode/test-electron's changelog.

Changelog

Commits

• See full diff in compare view

[Copilot]

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates the VS Code Electron test dependency version in package.json.

Changes:

• Bumped @vscode/test-electron from ^2.4.1 to ^3.1.0.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Akanksha Jain (jainakanksha-msft)]

Dependabot (@dependabot) rebase

[github-actions]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version) from the PR diff/description, search the codebase for where that dependency is actually used, and summarize what could be affected.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line summary of any code changes made).
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — post a final comment explaining why this update matters, what the impact/risk is, and what could go wrong if it weren't applied, along with your self-rating and reasoning.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version) from the PR diff/description, search the codebase for where that dependency is actually used, and summarize what could be affected.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line summary of any code changes made).
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — post a final comment explaining why this update matters, what the impact/risk is, and what could go wrong if it weren't applied, along with your self-rating and reasoning.

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version) ...

Done in 9c4a239.

Impact: @vscode/test-electron is only used in tests/upgrade/vsixLifecycle/installAndRunVsixSession.ts (via downloadAndUnzipVSCode, resolveCliArgsFromVSCodeExecutablePath, runTests), which powers the test:upgrade:vsix VSIX lifecycle/upgrade suite. Comparing the 2.5.2 → 3.1.0 changelog and the package's shipped .d.ts, none of these three APIs changed signature — the bump only raises the package's own Node engine requirement to >=22, which the repo already requires and enforces in CI.

Verification:

• npm ci --legacy-peer-deps, npm run build, npm run lint all pass cleanly, no merge conflicts.
• No test code needed to change since the consumed API is unaffected; a targeted run of test:upgrade:vsix fails only on getaddrinfo ENOTFOUND update.code.visualstudio.com — expected, since this sandbox has no network access to download a VS Code binary. It runs in .github/workflows/UpgradeCompatibility.yml in CI where network access is available.
• Added a ChangeLog.md entry under ## Upcoming Release → General: documenting the bump and the API-compatibility verification.

Risk if not applied: staying on 2.5.2 keeps the VSIX test harness on an old, unmaintained release; no known breaking risk from applying it here since the API surface used is unchanged.

Self-rating: 9/10 — correctness, build/lint health, and changelog accuracy are solid and verified; docked one point only because the VSIX suite itself couldn't be exercised end-to-end in this sandbox due to lack of network access (it will run in the UpgradeCompatibility.yml CI workflow).

[Akanksha Jain (jainakanksha-msft)]

Copilot, Make the changelog entry crisp enough.

[Copilot]

Copilot, Make the changelog entry crisp enough.

Tightened in 98260c6.