Skip to content

extension: require VS Code 1.112 - #2400

Closed
joshspicer wants to merge 2 commits into
mainfrom
agents/draft-pr-vscode-js-debug-compatibility
Closed

extension: require VS Code 1.112#2400
joshspicer wants to merge 2 commits into
mainfrom
agents/draft-pr-vscode-js-debug-compatibility

Conversation

@joshspicer

Copy link
Copy Markdown
Member

Summary

  • require VS Code 1.112 or newer, the first shipped stable product that authorizes the browser proposal for ms-vscode.js-debug
  • update the root lockfile metadata to match the source manifest
  • cover stable and nightly packages, whose generated manifests both inherit the source engine range

Compatibility evidence

  • shipped VS Code 1.111.0 does not authorize browser for either ms-vscode.js-debug or ms-vscode.js-debug-nightly
  • shipped VS Code 1.112.0 authorizes browser for both extension IDs
  • the pending mandatory compatibility gate rejects the old ^1.80.0 range and accepts both rebuilt VSIXes with ^1.112.0 across 35 admitted released stable products through VS Code 1.135.0

Validation

  • npm run compile -- package:prepare
  • npm run compile -- package:prepare --nightly
  • proposed-API compatibility validation for both generated VSIXes
  • npm run test:types
  • git diff --check

Tracking

joshspicer and others added 2 commits August 26, 2026 19:44
Align the declared engine range with the browser proposed API authorization floor.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@joshspicer joshspicer closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant