Upgrade vscode-ripgrep's yarn.lock entry so we pick-up latest #8280
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.
What it does
Upgrade
vscode-ripgrep
's yarn.lock entry so we pick-up latestThis will benefit the developers that build our example application behind a firewall, since
vscode-ripgrep
recently supports operating system environment proxy settings:microsoft/vscode-ripgrep#10
Extenders can upgrade their own application's
yarn.lock
since this change will not directly affect themFixes #8171
How to test
Build using
yarn
and confirm thatvscode-ripgrep
we pull is now1.8.0
:Test that
search-in-workspace
andfile-search
still workReview checklist
Reminder for reviewers