GitHub has disabled SHA-1 in HTTPS — from issue No. 032nofeed.dev
No Feed
Issue No. 032 · 16 September 2026
Breaking

GitHub has disabled SHA-1 in HTTPS

On 15 September GitHub completed a sunset it had scheduled in advance: SHA-1 in HTTPS is now off for github.com and partner CDNs, including Enterprise Cloud and Enterprise Cloud with Data Residency. Enterprise Server is unaffected.2

MATTERS TO · Anyone whose pipeline still builds on an old base image. A TLS stack that only offers SHA-1 signature algorithms can no longer reach github.com, and it surfaces as a handshake failure in a clone that worked on Monday. Audit the oldest image in your CI first.
WHAT THE VERDICT MEANS
Will break existing code: deprecation or API change.
Sources for this entry01 TypeSafe AI — Introducing System One Models & Jev, 15 Sep 2026 (2026-09-16) · 02 GitHub Changelog — SHA-1 in HTTPS on GitHub sunset, 15 Sep 2026 (2026-09-16) · 03 Google — Build real-time voice applications with Gemini 3.8 Live, 15 Sep 2026 (2026-09-16) · 04 Google — Gemini 3.8 Live & 3.8 Live Extended Thinking, 15 Sep 2026 (2026-09-16) · 05 Anthropic Status — error spikes, Claude Mythos 5.1 and Fable 5.1, 15 Sep 2026 (2026-09-16) · 06 arXiv 2609.17394 — Coding Agents Have Converged, 15 Sep 2026 (2026-09-16) · 07 Strix — admin access to Baseten GitHub repos, 1 Sep 2026 (2026-09-16) · 08 9to5Google — Gemini 3.8 Live announced, 15 Sep 2026 (2026-09-16) · 09 OpenAI Status — elevated errors, gpt-image-2.5-flare, 15 Sep 2026 (2026-09-16) · 10 Hacker News — Introducing System One Models and Jev, 1,085 points (2026-09-16)

Also in this issue

read the whole thing →
Use itGemini 3.8 Live and 3.8 Live Extended Thinking, in the API today

Get it by email.

One issue every weekday. The whole thing, not a teaser.

Or RSS, if you would rather we never had your address.