GitHub Enterprise Server (GHES) 3.21 enhances deployment efficiency, monitoring capabilities, code security, and policy management. Here are a few highlights in the 3.21 release:
- Organization custom properties are now generally available, giving enterprise administrators a way to tag organizations with metadata and automatically target enterprise rulesets. For more information, see organization custom properties.
-
Hierarchy view for GitHub Projects is now generally available. You can now view your full issue hierarchy directly in project table views, giving you clear visibility into complex work breakdowns without losing context or switching views. For more information, see hierarchy view.
-
REST API version
2026-03-10is now available and introduces breaking changes. Existing integrations on version2022-11-28will continue to be fully supported for at least 24 months from the 3.21 release date. For more information, see REST API version 2026-03-10. -
GitHub Actions workflow pages now successfully render workflows with more than 300 jobs. We’ve implemented lazy loading to smoothly handle large workflows. In addition, you can now filter jobs based on status (e.g.,
failedorin-progress) directly from the workflow pages. For more information, see improved performance for GitHub Actions workflows page. -
This version includes improvements to alert-level and enterprise-level permissions for secret scanning. You can now more easily manage secret scanning alerts, custom patterns, and push protection bypasses. For more information, see enterprise governance and policy improvements for secret scanning.
-
Configuring multiple data disks to host MySQL and repository data is now generally available. This applies to standalone and high availability topologies and is available in the latest patches of 3.17, 3.18, 3.19, and 3.20, and in 3.21. For more information, see configuring multiple data disks.
To learn more about GHES 3.21, check out the release notes, or download it now. If you have any issues upgrading to version 3.21 or experience any issues using these new features, please contact our support team.
Join the community discussion to share your feedback and ask questions.