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

chore(deps): update dependency cli/cli to v2.27.0 #5

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2023

Mend Renovate

This PR contains the following updates:

Package Update Change
cli/cli minor v2.2.0 -> v2.27.0

Release Notes

cli/cli

v2.27.0: GitHub CLI 2.27.0

Compare Source

v2.27.0

This is primarily an out of band bugfix release for codespaces users, but does include a new command gh run delete.

New Features

Bugfixes

New Contributors

Full Changelog: cli/cli@v2.26.1...v2.27.0-pre0

v2.26.1: GitHub CLI 2.26.1

Compare Source

What's Changed

Full Changelog: cli/cli@v2.26.0...v2.26.1

v2.26.0: GitHub CLI 2.26.0

Compare Source

gh 2.26.0

Important: credentials now stored securely by default

When running gh auth login, your credentials will now be stored in your operating system's credential storage instead of directly on disk. In other words, --secure-storage is now default behavior. We've added a new flag, --insecure-storage, to opt into the old insecure behavior in case you need to debug an issue with credential storage.

As before, to take advantage of credential storage, please re-run gh auth login.

For more context, you can read the v2.24.0 release notes

Ref: secure storage by default by @​vilmibm in https://github.com/cli/cli/pull/7276

Other new features

Bugfixes

Docs and development changes

New Contributors

Full Changelog: cli/cli@v2.25.1...v2.26.0-pre0

v2.25.1: GitHub CLI 2.25.1

Compare Source

What's Changed

Full Changelog: cli/cli@v2.25.0...v2.25.1

v2.25.0: GitHub CLI 2.25.0

Compare Source

What's New

What's Changed

New Contributors

Full Changelog: cli/cli@v2.24.3...v2.25.0

v2.24.3: GitHub CLI 2.24.3

Compare Source

What's Changed

Full Changelog: cli/cli@v2.24.2...v2.24.3

v2.24.2: GitHub CLI 2.24.2

Compare Source

What's Changed

Full Changelog: cli/cli@v2.24.1...v2.24.2

v2.24.1: GitHub CLI 2.24.1

Compare Source

What's Changed

Full Changelog: cli/cli@v2.24.0...v2.24.1

v2.24.0: GitHub CLI 2.24.0

Compare Source

What's New

Option to store gh access token in system encrypted storage

The gh auth login and gh auth refresh commands gained the new --secure-storage flag. In this mode, the access token that GitHub CLI uses for GitHub API requests will now be stored in the system keyring instead of in the plain text config file.

To migrate as an existing GitHub CLI user, re-authenticate like so:

gh auth refresh --secure-storage -h github.com

Depending on your system, you could get an interactive prompt to allow the CLI tool to access the system keyring. The systems that are supported are:

  • Keychain on macOS
  • GNOME Keyring on Linux (Secret Service dbus interface)
  • Wincred on Windows

Please note:

  • This feature is currently opt-in, but will become the default in the near future.

  • If none of the system storage providers are found, or the store operation fails, the token will be written to the config file as before.

  • Using this feature could result in Go extensions breaking if they were not updated to the latest go-gh version. If extensions you are using no longer work after migrating your token to secure token storage, please report the issue to that extension's repository.

  • Storing tokens in system keyring most likely won't work in “headless” environments.

Other additions

What's Changed

New Contributors

Full Changelog: cli/cli@v2.23.0...v2.24.0

v2.23.0: GitHub CLI 2.23.0

Compare Source

What's New

What's Changed

Full Changelog: cli/cli@v2.22.1...v2.23.0

v2.22.1: GitHub CLI 2.22.1

Compare Source

What's Changed

New Contributors

Full Changelog: cli/cli@v2.22.0...v2.22.1

v2.22.0: GitHub CLI 2.22.0

Compare Source

What's New

What's Changed

New Contributors

Full Changelog: cli/cli@v2.21.2...v2.22.0

v2.21.2: GitHub CLI 2.21.2

Compare Source

What's Changed

New Contributors

Full Changelog: cli/cli@v2.21.1...v2.21.2

v2.21.1: GitHub CLI 2.21.1

Compare Source

What's Changed

Full Changelog: cli/cli@v2.21.0...v2.21.1

v2.21.0: GitHub CLI 2.21.0

Compare Source

What's New

Selecting a default repository

When running a gh command for the first time in a local git repository that has multiple git remotes, gh used to interactively ask Which should be the base repository? so that the user may choose the git remote to default to when making queries to GitHub repositories. This had several problems:

  • Some users did not fully understand what they are being asked to choose;
  • The term “base repository” isn't an established GitHub term, except in the context of Pull Requests;
  • Once chosen, the only way to undo or change the choice made was to manually edit .git/config in the local repository.

The new behavior is as follows:

  • gh commands in a repository with multiple remotes will now error out until a default has been chosen.
  • The new gh repo set-default command can be used to select a default, view the selected value, or undo the selection altogether.

Thank you @​bchadwic and @​vilmibm! https://github.com/cli/cli/pull/4859 https://github.com/cli/cli/pull/6738

Internal git operations are now always authenticated

Previously, it could be confusing that a properly authenticated gh repo clone <repo> command could fail with a prompt for GitHub password. The underlying reason was that gh repo clone would shell out to git clone <url>, and from then on the authentication was entirely up to git's own credential management. If git wasn't set up to authenticate to GitHub, this could result in a generic password prompt, which appeared as if it was coming from gh.

The best general solution for setting up git to use credentials from GitHub CLI is to run gh auth setup-git. However, in this release, gh ensures that all underlying git operations are authenticated by gh, even if git on its own wasn't configured with a credential helper.

The way this works is by injecting extra configuration arguments when shelling out to git:

git -c credential.helper='!gh auth git-credential' clone <url>

Thank you @​samcoe! https://github.com/cli/cli/pull/6541

The gh api command now accepts nested JSON parameters

The gh api command is similar to the popular curl tool, but with JSON encoding & parsing support and with built-in GitHub authentication. Sending JSON POST parameters was as easy as:

gh api <endpoint> -f 'param1=value1' -f 'param2=value2'

Now there is also a way to send nested JSON objects and arrays via a special brackets syntax when specifying field names:

gh api <endpoint> -f 'head[branch][name]=main'

gh api <endpoint> -f 'labels[]=bug' -f 'labels[]=priority-1'

Thank you @​mislav! https://github.com/cli/cli/pull/6614

Other goodies

What's Changed

New Contributors

Full Changelog: cli/cli@v2.20.2...v2.21.0

v2.20.2: GitHub CLI 2.20.2

Compare Source

What's Changed

Full Changelog: cli/cli@v2.20.1...v2.20.2

v2.20.1: GitHub CLI 2.20.1

Compare Source

What's Changed

New Contributors

Full Changelog: cli/cli@v2.20.0...v2.20.1

v2.20.0: GitHub CLI 2.20.0

Compare Source

What's New

What's Changed

Full Changelog: cli/cli@v2.19.0...v2.20.0

v2.19.0: GitHub CLI 2.19.0

Compare Source

What's New

What's Changed

New Contributors

Full Changelog: cli/cli@v2.18.1...v2.19.0

v2.18.1: GitHub CLI 2.18.1

Compare Source

What's Changed

Full Changelog: cli/cli@v2.18.0...v2.18.1

v2.18.0: GitHub CLI 2.18.0

Compare Source

New Commands and Flags

What's Changed

Other Changes

New Contributors

Full Changelog: cli/cli@v2.17.0...v2.18.0

v2.17.0: GitHub CLI 2.17.0

Compare Source

What's Changed

New Contributors

Full Changelog: cli/cli@v2.16.1...v2.17.0

v2.16.1: GitHub CLI 2.16.1

Compare Source

What's Changed


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@murn0 murn0 merged commit c2d89f2 into master Apr 25, 2023
@renovate renovate bot deleted the renovate/cli-cli-2.x branch April 25, 2023 07:24
@github-actions github-actions bot added this to the v0.1.0 milestone Aug 9, 2023
@murn0 murn0 bot mentioned this pull request Aug 9, 2023
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.

None yet

1 participant