GHE.com 10月7日起弃用仅X25519 TLS连接
X25519-only TLS ends for GHE.com on October 7
依赖 GitHub API 的核心工具必须检查 TLS 配置，否则 10 月 7 日后将彻底断连。请排查代理与 SDK 是否禁用了 P-256/P-384 并提前升级。
Beginning October 7, 2026, GitHub Enterprise Cloud with data residency will no longer accept TLS connections from clients that offer only X25519 for key agreement.
自2026年10月7日起，具有数据驻留功能的GitHub Enterprise Cloud将不再接受仅提供X25519用于密钥协商的客户端的TLS连接。
Most customers don’t need to take action. The affected endpoints will continue to support the FIPS-approved P-256 (secp256r1) and P-384 (secp384r1) groups. Current browsers, operating systems, GitHub CLI releases, and commonly used TLS libraries already support P-256.
大多数客户无需采取任何操作。受影响的端点将继续支持FIPS批准的P-256（secp256r1）和P-384（secp384r1）曲线组。当前的浏览器、操作系统、GitHub CLI版本以及常用的TLS库均已支持P-256。
You may be affected if an application, proxy, security appliance, or TLS library is explicitly configured to offer only X25519. Before October 7, 2026, you should:
如果您的应用程序、代理、安全设备或TLS库被明确配置为仅使用X25519，则可能会受到影响。在2026年10月7日之前，您应该：
- Update your operating system, runtime, GitHub CLI, proxy, and TLS libraries to supported versions.
- Remove any X25519-only configuration.
- Ensure P-256 (secp256r1) is enabled. You may also enable P-384 (secp384r1).
- 将您的操作系统、运行时环境、GitHub CLI、代理和TLS库更新到支持的版本。
- 移除任何仅限X25519的配置。
- 确保已启用P-256（secp256r1）。您也可以启用P-384（secp384r1）。
After October 7, X25519-only clients will be unable to establish HTTPS connections. This change applies only to GitHub Enterprise Cloud with data residency. SSH connectivity is not affected.
10月7日之后，仅支持X25519的客户端将无法建立HTTPS连接。此更改仅适用于具有数据驻留功能的GitHub Enterprise Cloud。SSH连接不受影响。
If you need help validating your TLS configuration, contact GitHub Support.
如果您需要帮助来验证TLS配置，请联系GitHub Support。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力