The GitHub Enterprise Server 3.2 Release Candidate is available

The GitHub Enterprise Server 3.2 Release Candidate is available. This release includes more than 70 new features and changes to improve the developer experience and deliver new security capabilities for our customers.

Read the blog to discover the highlights in this release. Or, dive into the full GitHub Enterprise Server 3.2 release notes, and download it today.

Release Candidates are a way for you to try the latest features at the earliest time, and they help us gather feedback early to ensure the release works in your environment. They should be tested on non-production environments.

You can now download a CSV while will include each students' GitHub alias, roster identifier, individual grade, and more for any given Assignment. No action is needed by you to use this feature.

On the Assignment overview page, you will now see a dropdown with an option to "Download grades." This is also the new home for the "Download repositories" functionality.

download-grades

For feedback or questions on this feature, please use our GitHub Education Community Forum

See more

The npm registry will upgrade its public CouchDB instance on September 15, 2021. As part of this upgrade, we will promote a new CouchDB replica to become our new public CouchDB instance, https://replicate.npmjs.com. This upgrade will reset the CouchDB sequence number.

If you are not familiar with CouchDB replication, then you will not be impacted by this change. In particular, users running npm install or running other commands using the npm CLI will not be affected by this change.

If you replicate our public CouchDB or have an application that is following it, then you may be impacted:

  • If you are replicating the npm database using CouchDB then you may see a replication delay while your follower re-synchronizes, but you do not need to take any other action.

  • If you have custom tools that query npm's databases using the CouchDB Replication Protocol then you should ensure that you do not assume that sequence numbers are monotonically increasing, and that your custom replica correctly treats the sequence number as an opaque blob.

See more