releases.shpreview

v2.24.0

GitHub CLI 2.24.0

$npx -y @buildinternet/releases show rel_nDcuzXrH-U1SYmMaCENfB

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: https://github.com/cli/cli/compare/v2.23.0...v2.24.0

Fetched April 8, 2026