What changes at sign-in
GitHub is offering a public preview of expiring OAuth credentials in its command-line application. Starting with version 2.103.0, users can request this mode at login. The CLI stores an access token and a rotating refresh token, then renews the access credential when needed.
The feature is optional, so an existing login does not automatically change. GitHub says support is available on github.com and ghe.com, with GitHub Enterprise Server support beginning at version 3.23. An unsupported server can fall back to a nonexpiring credential.
The integration detail to check
A script that copies a token once and expects it to remain valid can stop working when that token expires. GitHub recommends letting the CLI retrieve a fresh credential when needed and using its credential-helper integration for Git over HTTPS. The company also recommends Git 2.46 or later for handling expiry information.
CGH perspective
Shorter access-token lifetimes can reduce the period in which a copied access token remains useful, but they do not remove the need to protect stored refresh credentials. Before changing a shared workflow, inventory where its tokens are obtained and cached. Test a complete renewal cycle and a failed-renewal case. That would reveal compatibility problems more reliably than a successful first login. CGH has not tested this preview across enterprise configurations.