releases.shpreview
GitHub/GitHub CLI

GitHub CLI

$npx -y @buildinternet/releases show github-cli
Mon
Wed
Fri
AprMayJunJulAugSepOctNovDecJanFebMarApr
Less
More
Releases10Avg3/moVersionsv2.85.0 → v2.90.0
Jul 30, 2025
GitHub CLI 2.76.2

gh pr create regression fix

This release fixes a regression introduced in v2.76.1 where organization teams were not present in prompts for pull request reviewers. This caused problems in multiple commands:

  • Interactive gh pr create could not select teams when adding pull request reviewers
  • Tab completions with gh pr create --reviewer flag did not present a list of organization teams
  • Tab completions with gh pr edit --add-reviewer flag did not present a list of organization teams
  • Tab completions with gh pr edit --remove-reviewer flag did not present a list of organization teams

For more information, see https://github.com/cli/cli/issues/11403

What's Changed

🐛 Fixes

📚 Docs & Chores

Full Changelog: https://github.com/cli/cli/compare/v2.76.1...v2.76.2

Jul 23, 2025
GitHub CLI 2.76.1

gh pr create regression fix

This release fixes a regression introduced in v2.76.0 where organization teams were retrieved outside of intentional use cases. This caused problems for GitHub Enterprise Server users using the GitHub Actions automatic token that does not have access to organization teams.

For more information, see https://github.com/cli/cli/issues/11360

What's Changed

🐛 Fixes

📚 Docs & Chores

Full Changelog: https://github.com/cli/cli/compare/v2.76.0...v2.76.1

Jul 17, 2025
GitHub CLI 2.76.0

:copilot: Copilot Coding Agent Support

GitHub Copilot Pro+ and Copilot Enterprise subscribers can now assign issues to GitHub Copilot during issue creation using:

  • Command-line flag: gh issue create --assignee @copilot
  • Launching web browser: gh issue create --assignee @copilot --web
  • Or interactively selecting Copilot (AI) as assignee in gh issue create metadata

For more details, refer to the full changelog post for Copilot coding agent.

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

Full Changelog: https://github.com/cli/cli/compare/v2.75.1...v2.76.0

Jul 14, 2025
GitHub CLI 2.75.1

What's Changed

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.75.0...v2.75.1

Jul 9, 2025
GitHub CLI 2.75.0

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.74.2...v2.75.0

Jun 18, 2025
GitHub CLI 2.74.2

What's Changed

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.74.1...v2.74.2

Jun 10, 2025
GitHub CLI 2.74.1

What's Changed

Full Changelog: https://github.com/cli/cli/compare/v2.74.0...v2.74.1

May 29, 2025
GitHub CLI 2.74.0

Security

A security vulnerability has been identified in a core gh dependency, go-gh, where an attacker-controlled GitHub Enterprise Server could result in executing arbitrary commands on a user's machine by replacing HTTP URLs provided by GitHub with local file paths for browsing.

This issue is addressed in this gh release by updating go-gh to a fixed version.

For more information, see https://github.com/cli/go-gh/security/advisories/GHSA-g9f5-x53j-h563

What's changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.73.0...v2.74.0

May 19, 2025
GitHub CLI 2.73.0

:copilot: Copilot Coding Agent Support

You can now assign issues to GitHub Copilot directly from gh, just as you would assign them to a teammate. Use gh issue edit <number> --add-assignee @copilot to assign the GitHub Copilot coding agent, and Copilot will work in the background to understand the issue, propose a solution, and open a pull request when it's ready for your review. If you run gh issue edit interactively, Copilot (AI) will be displayed as a potential assignee. This feature is available for GitHub Copilot Pro+ and Copilot Enterprise subscribers. For more details, refer to the full changelog post for Copilot coding agent.

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

What's Changed

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.72.0...v2.73.0

Apr 30, 2025
GitHub CLI 2.72.0

:accessibility: Accessibility public preview

This release marks the public preview of several accessibility improvements to the GitHub CLI that have been under development over the past year in partnership with our friends at Charm including:

  • customizable and contrasting colors
  • non-interactive user input prompting
  • text-based spinners

These new experiences are captured in a new gh a11y help topic command, which goes into greater detail into the motivation behind each of them as well as opt-in configuration settings / environment variables.

We would like you to share your feedback and join us on this journey through one of GitHub Accessibility feedback channels! 🙌

What's Changed

✨ Features

🐛 Fixes

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.71.2...v2.72.0

Apr 24, 2025
GitHub CLI 2.71.2

What's Changed

Full Changelog: https://github.com/cli/cli/compare/v2.71.1...v2.71.2

GitHub CLI 2.71.1

What's Changed

Full Changelog: https://github.com/cli/cli/compare/v2.71.0...v2.71.1

Apr 23, 2025
GitHub CLI 2.71.0

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.70.0...v2.71.0

Apr 15, 2025
GitHub CLI 2.70.0

Accessibility

This release contains dark shipped changes that are part of a larger GitHub CLI accessibility preview still under development. More information about these will be announced later this month including various channels to work with GitHub and GitHub CLI maintainers on shaping these experiences.

Ensure table headers are thematically contrasting

cli/cli#8292 is a long time issue where table headers were difficult to see in terminals with light background. Ahead of the aforementioned preview, v2.70.0 has shipped changes that improve the out-of-the-box experience based on terminal background detection.

The following screenshots demonstrate the Mac Terminal using the Basic profile, which responds to user's appearance preferences:

<img width="1512" alt="Screenshot of gh repo list in light background terminal" src="https://github.com/user-attachments/assets/87413dde-eec8-43eb-9c16-dc84f8249ddf" /> <img width="1512" alt="Screenshot of gh repo list in dark background terminal" src="https://github.com/user-attachments/assets/7430b42c-7267-402b-b565-a296beb4d5ea" />

For more information including demos from various official distributions, see cli/cli#10649.

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.69.0...v2.70.0

Mar 19, 2025
GitHub CLI 2.69.0

What's Changed

Features

Bug Fixes

Other

New Contributors

Full Changelog: https://github.com/cli/cli/compare/v2.68.1...v2.69.0

Mar 6, 2025
GitHub CLI 2.68.1

What's Changed

Full Changelog: https://github.com/cli/cli/compare/v2.68.0...v2.68.1

Mar 5, 2025
GitHub CLI 2.68.0

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

Feb 11, 2025
GitHub CLI 2.67.0

Security

A bug in gh attestation verify may return an incorrect zero exit status when no matching attestations are found for the specified --predicate-type <value> or the default https://slsa.dev/provenance/v1 if not specified. This issue only arises if an artifact has an attestation with a predicate type different from the one provided in the command. As a result, users relying solely on these exit codes may mistakenly believe the attestation has been verified, despite the absence of an attestation with the specified predicate type and the tool printing a verification failure.

Users are advised to update gh to version v2.67.0 as soon as possible.

For more information, see https://github.com/cli/cli/security/advisories/GHSA-fgw4-v983-mgp8

gh pr checkout now supports interactively selecting a pull request

Similar to commands like gh workflow run which prompts for a workflow to run, now gh pr checkout will prompt for a pull request to checkout. The list is currently limited to the most recent 10 pull requests in the repository.

https://github.com/user-attachments/assets/0b2e3761-7318-4573-8a23-ae6f1a44b018

Big thank you to @nilvng for implementing this 🙌

Contributing guidelines updated

We've updated our CONTRIBUTING.md guidelines to give more clarity around old help wanted issues.

TLDR:

  • Please directly mention @cli/code-reviewers when an issue you want to work on does not have clear Acceptance Criteria
  • Please only open pull requests for issues with both the help wanted label and clear Acceptance Criteria
  • Please avoid expanding pull request scope to include changes that are not described in the connected issue's Acceptance Criteria

Note: Acceptance Criteria is posted as an issue comment by a core maintainer.

See https://github.com/cli/cli/pull/10381 and https://github.com/cli/cli/pull/10395 for more information.

❓ Have feedback on anything? We'd love to hear from you in a discussion post ❤️

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

Full Changelog: https://github.com/cli/cli/compare/v2.66.1...v2.67.0

Jan 31, 2025
GitHub CLI 2.66.1

Hotfix: gh pr view fails with provided URL

This addresses a regression in gh pr view was reported in #10352. This regression was due to a change in v2.66.0 that no longer allowed gh pr subcommands to execute properly outside of a git repo.

What's Changed

Full Changelog: https://github.com/cli/cli/compare/v2.66.0...v2.66.1

Jan 30, 2025
GitHub CLI 2.66.0

gh pr view and gh pr status now respect common triangular workflow configurations

Previously, gh pr view and gh pr status would fail for pull request's (PR) open in triangular workflows. This was due to gh being unable to identify the PR's corresponding remote and branch refs on GitHub.

Now, gh pr view and gh pr status should successfully identify the PR's refs when the following common git configurations are used:

Branch specific configuration, the former, supersedes repo specific configuration, the latter.

Additionally, if the @{push} revision syntax for git resolves for a branch, gh pr view and gh pr status should work regardless of additional config settings.

For more information, see

gh secret list, gh secret set, and gh secret delete now require repository selection when multiple git remotes are present

Previously, gh secret list, gh secret set, and gh secret delete would determine which remote to target for interacting with GitHub Actions secrets. Remotes marked as default using gh repo set-default or through other gh commands had higher priority when figuring out which repository to interact with. This could have unexpected outcomes when using gh secret commands with forked repositories as the upstream repository would generally be selected.

Now, gh secret commands require users to disambiguate which repository should be the target if multiple remotes are present and the -R, --repo flag is not provided.

For more information, see https://github.com/cli/cli/issues/4688

Extension update notices now notify once every 24 hours per extension and can be disabled

Previously, the GitHub CLI would notify users about newer versions every time an extension was executed. This did not match GitHub CLI notices, which only notified users once every 24 hours and could be disabled through an environment variable.

Now, extension update notices will behave similar to GitHub CLI notices. To disable extension update notices, set the GH_NO_EXTENSION_UPDATE_NOTIFIER environment variable.

For more information, see https://github.com/cli/cli/issues/9925

What's Changed

✨ Features

🐛 Fixes

📚 Docs & Chores

:dependabot: Dependencies

New Contributors

Big thank you to our many new and longtime contributors making this release happen!! ❤️ ✨

Full Changelog: https://github.com/cli/cli/compare/v2.65.0...v2.66.0

Latest
v2.90.0
Source
@cli/cli
Tracking Since
Jan 27, 2023
Last fetched Apr 18, 2026