What happened
GitHub announced on the GitHub Changelog that the PGP key currently used to sign GitHub CLI Linux package repositories will expire on Saturday, September 5, 2026.
According to the notice, APT and RPM repository metadata will be affected beginning with the first GitHub CLI release issued after that expiration date.
Why it matters
For Linux users who rely on APT or RPM repositories to install GitHub CLI, this expiration marks a clear deadline: the first release after September 5 will involve changes to repository metadata. Users may need to review their setup once that release arrives.
An expiring signing key can affect how package managers trust repository metadata, so anyone maintaining automated installs or update pipelines should keep an eye on GitHub's release notes around that time.
Key facts
The GitHub CLI Linux package signing key expires on Saturday, September 5, 2026.
The key is a PGP key for GitHub CLI Linux package repositories.
Beginning with the first release after September 5, APT and RPM repository metadata will be affected.
The announcement was posted on the GitHub Changelog on September 3, 2026.
What to watch next
The next GitHub CLI release after September 5, 2026, will show how APT and RPM repository metadata is handled.
The GitHub Changelog may provide further instructions or announcements about the signing key as the expiration approaches.