joao.dubas/ide
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

chore(deps): update dependency github-cli to v2.62.0 #112

Merged
joao.dubas merged 1 commits from renovate/github-cli-2.x into main 2024-11-22 11:20:50 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2024-11-14 16:24:34 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
github-cli minor 2.61.0 -> 2.62.0

Release Notes

cli/cli (github-cli)

v2.62.0: GitHub CLI 2.62.0

Compare Source

What's Changed

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

Security

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.

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 Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [github-cli](https://github.com/cli/cli) | minor | `2.61.0` -> `2.62.0` | --- ### Release Notes <details> <summary>cli/cli (github-cli)</summary> ### [`v2.62.0`](https://github.com/cli/cli/releases/tag/v2.62.0): GitHub CLI 2.62.0 [Compare Source](https://github.com/cli/cli/compare/v2.61.0...v2.62.0) #### What's Changed - Update monotonic verification logic and testing by [@&#8203;malancas](https://github.com/malancas) in https://github.com/cli/cli/pull/9856 - Check extension for latest version when executed by [@&#8203;andyfeller](https://github.com/andyfeller) in https://github.com/cli/cli/pull/9866 - Shorten extension release checking from 3s to 1s by [@&#8203;andyfeller](https://github.com/andyfeller) in https://github.com/cli/cli/pull/9914 - Mention GitHub CLI team on discussion issues by [@&#8203;andyfeller](https://github.com/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: ```shell $ 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. </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMzMuMSIsInVwZGF0ZWRJblZlciI6IjM4LjEzMy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2024-11-14 16:24:35 +00:00
joao.dubas force-pushed renovate/github-cli-2.x from c1e84d380c to 317c1562f0 2024-11-22 11:12:34 +00:00 Compare
joao.dubas merged commit b05ca0bf8b into main 2024-11-22 11:20:50 +00:00
joao.dubas deleted branch renovate/github-cli-2.x 2024-11-22 11:20:50 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot joao.dubas
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: joao.dubas/ide#112
No description provided.
Delete Branch "renovate/github-cli-2.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?