{"id":95433,"date":"2026-04-20T07:15:30","date_gmt":"2026-04-20T14:15:30","guid":{"rendered":"https:\/\/github.blog\/changelog\/2026-04-20-sunsetting-sha-1-in-https-on-github"},"modified":"2026-04-20T09:30:12","modified_gmt":"2026-04-20T16:30:12","slug":"sunsetting-sha-1-in-https-on-github","status":"publish","type":[3523],"link":"https:\/\/github.blog\/changelog\/2026-04-20-sunsetting-sha-1-in-https-on-github","title":{"rendered":"Sunsetting SHA-1 in HTTPS on GitHub"},"content":{"rendered":"\n

What’s changing<\/span><\/a><\/h2>\n

We’re going to remove the use of SHA-1 in HTTPS for GitHub and our CDNs. This impacts browsers that are used to view the GitHub website, any software that uses the GitHub API, and Git clients that push and pull over HTTPS. These changes will be made to github.com, including GitHub Enterprise Cloud and GitHub Enterprise Cloud with Data Residency. GitHub Enterprise Server will not be affected.<\/p>\n

Deprecation schedule<\/span><\/a><\/h2>\n

We will conduct a brownout, where we temporarily disable SHA-1 to raise awareness around the deprecation. If you are impacted by the brownout, you will need to plan to add support for more modern TLS algorithms. Our planned schedule for SHA-1 deprecation and removal is as follows:<\/p>\n