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

New release 2.0.692 #642

Merged
merged 82 commits into from
Apr 1, 2022
Merged

New release 2.0.692 #642

merged 82 commits into from
Apr 1, 2022

Conversation

ldennington
Copy link
Contributor

Changes:

mminns and others added 30 commits December 10, 2021 11:22
… anything.

Stored credentials for Bitbucket.org are validated before returning.

Assume DC/Server credentials are good and rely on Git to try them and,
if necessary, ask GCM to ERASE invalid ones.

Add GCM_BITBUCKET_ALWAYS_REFRESH_CREDENTIALS/bitbucketAlwaysRefreshCredentials configuration option to revert to old behaviour

Added additional tests to hit > 66% test coverage for Atlassian.Bitbucket
…removed unused code and out of date comments
There has been a behaviour change in the System.CommandLine library.
Previously string arguments that were missing would be null, but now
they are the empty string.

Update downlevel use of the `organization` parameter in `BindCmd` to
also expect an empty/whitespace string, as well as null.
Fix bug in Azure Repos binding `list` command
Update the WSL documentation to point to the correct standalone
system-wide GCM install, and also add a section about using the standalone\
user-only installer.

The installation path is under `%LocalAppData%` in this case.
Add support for the user to select OAuth authentication in the first
credential prompt. Previously the user must either update their config
to remove the 'basic' auth mode, OR otherwise pass the initial
username/password prompt (for example with an app password).

Users can now signify they want to use OAuth immediately.
Add a new "Sign in with OAuth" button to the initial credentials prompt
for Bitbucket. This allows users to avoid typing in a username/password
at all.
Allow shortcut to perform OAuth from first prompt with Bitbucket
Use the correct window title for the GitHub device code dialog window.
Previously this was re-using the same title as the 2FA code window.
Use correct window title for device code in GitHub UI
Update package Nerdbank.GitVersioning
Add missing double quotes (") to the WSL documentation about using GCM
without Git for Windows.
Fix WSL instructions by adding missing quotes
Remove overzealous interactivity checks.
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Skip helper when no choice necessary
Default installation path now has "Core" in the name.
Add a new setting and environment variable that allows a user to disable
the use of GUI prompts (in favour of terminal/text-based ones where
available).
mjcheetham and others added 25 commits March 1, 2022 13:21
Windows Server 2016 does not support WAM, so we should not try to enable
the broker unless we're on Server 2019 and later.

Also update the Windows (client; non-server) version checks to be
tighter. Previously any major version of 10 or greater was considered
"supported", but this is wrong. Windows 10 build 15063 was the first to
support WAM.
Clarify that plaintext store is distinct from git-credential-store
Exclude Windows Server 2016 from WAM support
On custom GitLab instances, don't show the GitLab "fox" logo, only the
logotype. We also replace the old PNG logo with SVG/vector versions for
better display on high-resolution displays.

Ensure we only show the "sign up" link for GitLab.com

fix wpf
Pass the instance URL argument to the GitLab UI helper.
Add GUI prompts for GitLab authentication
Update build.sh to support install from source scenario.
Add script to help users automatically install from source on supported
distributions.
Add new GitHub actions workflow to validate install from source on
supported distributions.
Update README.md with instructions for downloading and running the
install from source script.
Fix GitHub Enterprise API URL for raw source code links.
Add `install-from-source.sh` and surrounding infrastructure
Remove build number from the release artifacts
Install the .NET 6.0 SDK and enforce a minimum NuGet version for macOS
signing workflow. This duplicates what we currently do in the Windows
workflow and fixes the .NET error observed in this attempted release
build:

https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=17051675&view=results

Clean test build with this change:

https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=17052160&view=results
…elease

.azure-pipelines: install .NET 6.0 sdk for macOS signing
@ldennington ldennington merged commit ff22f13 into release Apr 1, 2022
@ldennington ldennington changed the title New release 2.0.703 New release 2.0.692 Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants