跳到正文
GitHub Changelog· Allison·· 2 天前精选AI 评分63

GitHub Enterprise Server 3.23 候选发布版上线

GitHub Enterprise Server 3.23 release candidate

AI 导读

GitHub Enterprise Server 3.23 候选发布版现已开放下载,引入了多项平台级安全与管理新功能。新版本支持在隔离断网环境下通过纯 CPU 微调模型运行 AI 非结构化密钥检测,并为 Dependabot 引入默认 3 天的依赖包版本更新冷静期以防范恶意代码。

推荐理由

原文给出了离线 AI 密钥检测与 Dependabot 冷静期等具体机制,企业可以据此评估私有化部署的安全升级收益。

正文 · 原文

GitHub Enterprise Server (GHES) 3.23 is now available and introduces new capabilities across the platform. Here are a few highlights in the 3.23 release:

  • When working in GitHub Projects, you can create more precise project views by combining filters with logical OR, explicit AND, and parentheses for grouping. For example, (status:Done OR status:Todo) is:issue shows issues with either status.
  • If your enterprise uses GitHub Secret Protection, you can detect unstructured secrets entirely within your network using AI secret detection on GHES, including in air-gapped environments. A self-contained, fine-tuned model runs on the appliance’s CPU without a GPU, hosted LLM, or outbound connection. This feature is in public preview and subject to change.

  • As a developer, you can identify known malicious packages in PyPI, Maven, RubyGems, NuGet, Go, Rust, and Composer through the GitHub Advisory Database, in addition to npm. The database automatically ingests malware advisories from OpenSSF’s malicious-packages repository to expand coverage across these ecosystems.

  • By default, Dependabot waits until a package version has been available on its registry for at least three days before opening a version update pull request. This cooldown gives maintainers and the community more time to detect and report compromised or buggy releases before users merge updates.

  • As an OAuth app developer, you can limit token lifetimes by using access tokens that expire after eight hours and refresh tokens to obtain new access tokens. Token expiration is opt-in for existing OAuth apps and the default for newly created apps. You can request expiring tokens with scope=offline_access during authorization for testing and gradual rollout, or require expiration in your app registration. Before requiring expiration, you must update all clients to request, store, and use refresh tokens to avoid breaking sign-in for clients that do not support them. This feature is in public preview and subject to change.

  • In your GHES cluster, you can now move the Redis primary from a node that also runs other services, such as MySQL, to a dedicated node. Redis then uses the dedicated node’s resources and data volume rather than sharing them with those services. This procedure does not attach a new disk to an existing node or use an external Redis service.

Release candidates let you try the latest features early and share feedback before general availability. To learn more, see About upgrades to new releases and the GHES 3.23 release notes. To get started, download the GHES 3.23 release candidate.

If you have feedback or questions about the release candidate, contact GitHub Support.

The post GitHub Enterprise Server 3.23 release candidate appeared first on The GitHub Blog.

来源:GitHub Changelog · github.blog

EVAOO 主站实战落地 · AI Agent 与研发提效

看完情报?回到 EVAOO 主站直接上手工具与完整 SOP

返回 EVAOO 主站