feat(cli-tools): update cli/cli (v2.61.0 -> v2.62.0)#307
Merged
Conversation
Owner
|
🎉 This PR is included in version 1.12.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.61.0->2.62.0Release Notes
cli/cli (cli/cli)
v2.62.0: GitHub CLI 2.62.0Compare Source
What's Changed
Full Changelog: cli/cli@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 sshorgh codespace logscommands.For more information, see GHSA-p2h2-3vg9-4p87
GitHub CLI notifies users about latest extension upgrades
Similar to the notification of latest
ghreleases, thev2.62.0version of GitHub CLI will notify users about latest extension upgrades when the extension is used: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:
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.