Skip to content

chore(mise): update tool gh (2.102.1 → 2.103.0) - #90

Merged
home-infrastructure-renovate[bot] merged 1 commit into
mainfrom
renovate/mise-tools
Oct 24, 2026
Merged

home-infrastructure-renovate[bot] merged 1 commit into
mainfrom
renovate/mise-tools

Conversation

@home-infrastructure-renovate

@home-infrastructure-renovate home-infrastructure-renovate Bot commented Jul 24, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change Pending
gh tools minor 2.102.1 → 2.103.0 2.103.2 (+1)

Release Notes

cli/cli (gh)

v2.103.0: GitHub CLI 2.103.0

Compare Source

Expiring, auto-refreshing OAuth tokens (preview)

gh can now sign in with expiring OAuth credentials that it refreshes automatically. When you opt in, gh stores a short-lived access token alongside a rotating refresh token and refreshes the access token whenever it is needed, so you stay signed in without having to authenticate again.

To opt in for a single sign-in, run:

gh auth login --expiring

To prefer expiring credentials for every sign-in, run:

gh config set expiring_credentials enabled

gh auth status shows whether a credential is refreshable and when the current access token expires. Both gh auth status and gh auth token automatically refresh the access token when needed. Expiring tokens are available on github.com and GHE.com; on hosts that do not issue them, gh falls back to a regular non-expiring token.

If you use HTTPS as your git protocol, we advise using git 2.46 or newer and letting gh act as your git credential helper by running gh auth setup-git. This way gh serves and refreshes the expiring credential for git, and git does not cache it past its lifetime.

[!IMPORTANT]
Expiring access tokens should not be cached. Scripts and extensions that store the output of gh auth token will eventually hold an expired token, so run gh auth token again each time a token is needed. Tokens supplied through GH_TOKEN or GITHUB_TOKEN are never refreshed.

For more information, see Authenticating with GitHub CLI.

Manage issue artifacts with gh issue artifact (private preview)

gh issue artifact brings issue artifacts to the command line. Users and organizations enrolled in the private preview can use the list, view, create, edit, download, and delete commands to manage issue artifacts.

# Create a Markdown document with an attached image
gh issue artifact create 142 signin-plan.md --attach ./signin-flow.png

# Create an HTML document
gh issue artifact create 142 menu-prototype.html

# List or view artifacts
gh issue artifact list 142
gh issue artifact view 142 2

# Update a document or restore an earlier version
gh issue artifact edit 142 2 --body-file signin-plan-v2.md
gh issue artifact edit 142 2 --restore-version 5

Artifacts can also be addressed by their GitHub URLs, and Markdown documents support image and video attachments with --attach.

[!IMPORTANT]
Issue artifacts are in private preview. These commands only work for repositories enrolled in the preview. See the Issue Artifacts private preview announcement and feedback discussion for access instructions and to share feedback.

What's Changed

✨ Features
🐛 Fixes
📚 Docs & Chores
:dependabot: Dependencies

New Contributors

Full Changelog: cli/cli@v2.102.1...v2.103.0


Configuration

📅 Schedule: (UTC)

  • 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 8 times, most recently from 3dda0b6 to b08e7a8 Compare August 3, 2026 12:18
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 3 times, most recently from 2acfb14 to 0ab31bb Compare August 7, 2026 08:05
@home-infrastructure-renovate home-infrastructure-renovate Bot changed the title chore(mise): Update mise tools chore(mise): update mise tools Aug 13, 2026
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 4 times, most recently from 518bc81 to 98c4fae Compare August 24, 2026 08:35
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 4 times, most recently from 0c2b53c to 3d762a5 Compare September 12, 2026 05:37
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 3 times, most recently from d8c76b5 to 53b3f3c Compare September 18, 2026 17:05
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 4 times, most recently from a8bf869 to 0dd6360 Compare September 25, 2026 01:25
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 5 times, most recently from 7c4964a to 81bbdb6 Compare October 1, 2026 21:46
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 3 times, most recently from 3c45678 to 45c1efd Compare October 2, 2026 20:39
@home-infrastructure-renovate
home-infrastructure-renovate Bot force-pushed the renovate/mise-tools branch 2 times, most recently from 16979dc to dabee05 Compare October 24, 2026 13:58
@denniseffing
denniseffing force-pushed the main branch 2 times, most recently from 8e2d01a to 8277800 Compare October 24, 2026 17:00
@home-infrastructure-renovate home-infrastructure-renovate Bot changed the title chore(mise): update mise tools chore(mise): update tool gh (2.102.1 → 2.103.0) Oct 24, 2026
@home-infrastructure-renovate
home-infrastructure-renovate Bot merged commit 1a2f500 into main Oct 24, 2026
8 checks passed
@home-infrastructure-renovate
home-infrastructure-renovate Bot deleted the renovate/mise-tools branch October 24, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants