Repository navigation
chore(deps): safe updates — marked patch, webpack/ts-loader minors, VS Code types in lockfile - #19
Merged
Merged
Conversation
…t ships in the VSIX), webpack and ts-loader minors, and newer VS Code type definitions in the lockfile — engines stays 1.85+, so no user is asked to upgrade anything
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
^1.85.0, because vsce rejects a declared types range aboveengines.vscode— engines stays ^1.85.0, so no user is asked to upgrade their editorThis is the safe subset of #17, split out per the stable-upgrade policy: patches and minors flow; majors are deferred to the toolchain roadmap.
Verification
npm run lint✓npm test— 1174 tests ✓npm run package(webpack production) ✓npx @vscode/vsce package --no-dependencies✓ (VSIX builds, 11 files)Checklist
npm run lintpassesnpm testpasses