This only bites Linux users who install gh from GitHub's official APT or RPM repositories — Homebrew, the release tarballs, Windows, and macOS are all untouched. Back in April, GitHub published a keyring bundling both the current key and its replacement, so anyone who set up the repo since then is already covered. The catch is older installs: if your machine trusts only the expiring key, the first gh release after Saturday will be signed with a key it doesn't recognize, and apt or dnf will quietly refuse the update. Pull the new keyring now and skip the confused debugging session later. GitHub is doing this the careful way — in September 2024 the old key lapsed without warning and broke installs across the ecosystem, so this time they're rotating early and on purpose.