On November 4, GitHub did something it had been warning about since September: it turned off two legacy SSH algorithms for a day. Not a warning banner. Not a deprecation notice in a changelog you never read. The algorithms simply stopped working, and anyone whose setup still depended on them got a failed connection instead of a push.
If your git push worked fine that day, good. That probably means you were never at risk. But the brownout was only a rehearsal. The same switch flips again on December 9, and on January 13, 2027, the old algorithms are gone for good. If you push code over SSH — and if you run any automation that does — now is the time to check, while the fix is still a five-minute job and not a 2 a.m. incident.
What actually changed
GitHub announced the change on September 22, and it has four parts:
RSA signatures using SHA-1 are going away. In SSH terms, that is the ssh-rsa signature type, including RSA certificates that sign with SHA-1.…