v2.62.0

What's Changed

• Update monotonic verification logic and testing by @malancas in https://github.com/cli/cli/pull/9856
• Check extension for latest version when executed by @andyfeller in https://github.com/cli/cli/pull/9866
• Shorten extension release checking from 3s to 1s by @andyfeller in https://github.com/cli/cli/pull/9914
• Mention GitHub CLI team on discussion issues by @andyfeller in https://github.com/cli/cli/pull/9920

Full Changelog: https://github.com/cli/cli/compare/v2.61.0...v2.62.0

Security

• A security vulnerability has been identified in GitHub CLI that could allow remote code execution (RCE) when users connect to a malicious Codespace SSH server and use the gh codespace ssh or gh codespace logs commands.

  For more information, see https://github.com/cli/cli/security/advisories/GHSA-p2h2-3vg9-4p87

GitHub CLI notifies users about latest extension upgrades

Similar to the notification of latest gh releases, the v2.62.0 version of GitHub CLI will notify users about latest extension upgrades when the extension is used:

$ gh ado2gh
...

A new release of ado2gh is available: 1.7.0 → 1.8.0
To upgrade, run: gh extension upgrade ado2gh --force
https://github.com/github/gh-ado2gh

Why does this matter?

This removes a common pain point of extension authors as they have had to reverse engineer and implement a similar mechanism within their extensions directly.

With this quality of life improvement, there are 2 big benefits:

1. Extension authors will hopefully see increased adoption of newer releases while having lower bar to maintaining their extensions.
2. GitHub CLI users will have greater awareness of new features, bug fixes, and security fixes to the extensions used.

What do you need to do?

Extension authors should review their extensions and consider removing any custom logic previously implemented to notify users of new releases.