Skip to content

GitHub Enterprise Server 3.4 is now generally available

GitHub Enterprise Server 3.4 is Generally Available
We are excited to announce that the newest version of GitHub Enterprise Server is now available. This update includes enhancements to make developing software even easier for everyone with a host of improvements for security, compliance and administration teams. You can find all changes in the release notes, but here are a few highlights from the release:

  • Reusable workflows for GitHub Actions (#257)
  • Dependabot security updates (#343)
  • Ruby support for GitHub Advanced Security’s code scanning feature (#136)

Accompanying these new features are a collection of productivity enhancements for developers, including keyboard shortcuts, auto-generated release notes, and more.

  • Organizations can now publish a Read more.
  • Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments.
  • Automatically generated release notes. Read more.

To learn more about all the new features in GitHub Enterprise Server 3.4, read the release notes or download it today. Are you using the latest GitHub Enterprise Server version? Use the Upgrade Assistant to find the upgrade path from your current version of GitHub Enterprise Server to your desired version.

GitHub changed which keys are supported in SSH and removed the unencrypted Git protocol.
You can read more about the motivation behind these changes in our blog post from last September.
As a reminder, these changes were:

  • Removed all support for DSA keys
  • Required SHA-2 signatures on all RSA keys uploaded after November 2, 2021 (RSA keys uploaded prior to the cutoff may still use SHA-1 signatures)
  • Removed legacy SSH algorithms HMAC-SHA-1 and CBC ciphers
  • Permanently disabled the unencrypted Git protocol
See more

The npm Public Roadmap is being deprecated in favor of using the GitHub Public Roadmap to track feature launches for the npm Registry, CLI, and website.

Launched in October of 2020, the original npm roadmap process worked well for the team. As time has passed, the benefits of using a shared roadmap for GitHub and npm now outweigh the flexibility of managing separate ones. From now on, all large launches will be tracked via the GitHub Public Roadmap.

See more