-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
New release (attempt 2) #534
Merged
Merged
Conversation
This file contains 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
When installed inside of a Linux environment we typically look for a set of utilities to open the user's preferred browser (xdg-open, gnome-open, kfmclient). However, if we are actually in a WSL (Windows Subsystem for Linux) distribution, these utilties may not be/are not present. Instead we can try and use the `wslview` utility that will launch the user's browser on the _Windows host_. Appending `wslview` to the list of utilities to open the browser means no behaviour change for existing Linux users, but for WSL distros we now have a chance to still open the browser.
Update the System.CommandLine package to 2.0.0-beta1.21216.1 to hopefully fix some problems with dotnet-suggest registration caused by Process::UseShellExecute differences between .NET Framework and .NET (Core). jonsequitur/command-line-api@ad22b69 dotnet/command-line-api#1254 #505
As part of the migration of GCM out of the microsoft org, we removed packages from the Microsoft Hirsute/Bionic feeds. Adding a note to the README informing users that these packages are no longer available and that installing the debian package from the releases page is the preferred mode at this time.
…eadme README: add information on removal from MSFT Ubuntu feeds
Use the new Microbuild pool from 1ES.
Fix release builds
Update System.CommandLine to 2.0.0-beta1.21216.1
Use wslview to launch browser in Windows from WSL
vtbassmatt
approved these changes
Nov 16, 2021
Merged
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.
Follows on from release PR #530 that had some problems with the new build infrastructure:
NO_PROXY
contains a glob pattern #497, MatchNO_PROXY
formats to libcurl behaviour #501, Match libcurl lowercase proxy environment variable behaviour #503)credential.provider
after successful auto detection probe #517)Also bring in a few more changes that have happened in the interim:
wslview
command to open the browser (Use wslview to launch browser in Windows from WSL #529)