Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade vscode-ripgrep's yarn.lock entry so we pick-up latest #8280

Merged
merged 1 commit into from
Aug 1, 2020

Conversation

marcdumais-work
Copy link
Contributor

@marcdumais-work marcdumais-work commented Jul 31, 2020

What it does

Upgrade vscode-ripgrep's yarn.lock entry so we pick-up latest

This 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 them

Fixes #8171

How to test

Build using yarn and confirm that vscode-ripgrep we pull is now 1.8.0:

$ yarn why vscode-ripgrep
[...]
=> Found "vscode-ripgrep@1.8.0"

Test that search-in-workspace and file-search still work

Review checklist

Reminder for reviewers

@marcdumais-work marcdumais-work changed the title Upgrade vscode-ripgrep's yarn.lock entry so we pick-up latest Upgrade vscode-ripgrep's yarn.lock entry so we pick-up latest Jul 31, 2020
@vince-fugnitto vince-fugnitto added the dependencies pull requests that update a dependency file label Jul 31, 2020
Copy link
Member

@vince-fugnitto vince-fugnitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good, it should fix the main repo build for anyone who uses a proxy.
For example: #8282

It also is more permissive and allows downstream applications to use the vscode-ripgrep version which best suits them.

Fixes #8171

This will benefit the developres that build our example application behind
a firewall, since now `ripgrep` respects environment proxy settings.

Extenders can upgrade their own application's `yarn.lock` since this change
will not affect them.

Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
@marcdumais-work
Copy link
Contributor Author

Thanks for the review @vince-fugnitto . Can you have another quick look? I thought it would be good to add a CHANGELOG entry.

Copy link
Member

@vince-fugnitto vince-fugnitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me 👍

@marcdumais-work marcdumais-work merged commit f673eb4 into master Aug 1, 2020
@marcdumais-work marcdumais-work deleted the unpin-ripgrep branch November 8, 2022 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade vscode-ripgrep, to solve proxy issue
2 participants