GitHub APIBreaking changecritical

GitHub drops SHA-1 support for HTTPS connections on Sep 15, 2026

Detected
Sep 15, 2026
Effective
Sep 15, 2026(took effect 60 days ago)
Confidence
82%

What changed

GitHub has sunset SHA-1 in HTTPS connections, effective September 15, 2026. This is a permanent removal with no fallback, meaning clients relying on SHA-1 cipher suites for HTTPS communication with GitHub will be unable to connect.

What to do

Ensure all HTTPS clients, libraries, and tooling connecting to GitHub use SHA-2 (e.g., SHA-256) or stronger cipher suites. Upgrade outdated TLS stacks or dependencies that rely on SHA-1.

Affected

header: TLS/HTTPS SHA-1 cipher suite support

Source: github.blog (GitHub's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the GitHub SDK and the names above:

npm: @octokit/restnpm: @octokit/corenpm: octokitpip: PyGithubruby: octokitgo: github.com/google/go-githubphp: knplabs/github-apijava: org.kohsuke:github-apicsharp: Octokitrust: octocrab

Or let Breakwatch do it: connect a repo and see which files call GitHub, then get the next change as an alert pointing at those files. Check a repo free

Get GitHub API changes by email

Once a week: the breaking changes and upcoming deadlines for GitHub, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More GitHub API changes

Every GitHub API change →