Raise minimum VS Code version to 1.136 - #22
Merged
Merged
Conversation
This was referenced Sep 8, 2026
Merged
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.
Supersedes #21.
Dependabot's #21 bumped
@types/vscodeto 1.136.0 on its own, leavingengines.vscodeat^1.97.0. That combination failsvsce package:CI did not catch it, because
npm run packageistsc --noEmitplus esbuild and never validates the manifest. The failure would only have appeared in the release job, after thev*tag was already pushed.Changes
engines.vscodeand@types/vscodeboth move to^1.136.0, kept in the pairingvscerequires.vsce package, so the same class of manifest fault fails a pull request instead of a release.Unreleased.Compatibility
This raises the minimum supported VS Code version by 39 minor releases. Installations older than 1.136 keep the last compatible build from the Marketplace instead of updating.
No API forced this. The extension compiles cleanly against
@types/vscode@1.97.0, so^1.97.0was an accurate floor for the paste-provider API in use. Tracking the current release is a deliberate maintenance choice.Verification
Run locally on a clean
npm ci:npm test- 31 passed, 0 failednpm run package- cleannpx @vscode/vsce package- packaged, 64.66 KBextension/package.jsonreportsengines.vscode^1.136.0