GitHub confirmed the removal of SHA-1 support from HTTPS connections to github.com and associated services.
The change covers partner CDNs and GitHub Enterprise Cloud, including data residency deployments. GitHub Enterprise Server is unaffected. This is a transport-security change; the announcement is not a change to Git commit identifiers.
Source announcement: . This is an original summary, not independent on-the-ground reporting.
Last updated: . Editorial policy & corrections
Global
Trusted npm publishing configurations can now manage distribution tags using short-lived OIDC credentials.
Read update : npm adds opt-in tag management to trusted publishingGlobal
GitHub Team organizations can now start trials of Code Security and Secret Protection themselves.
Read update : GitHub Team gains self-serve Advanced Security trialsGlobal
GitHub Enterprise Cloud with data residency will stop accepting clients offering only X25519 key agreement on October 7.
Read update : GitHub warns of October 7 TLS change for data-residency customers