GitHub Upgrade – 3.9.5

On Thursday, September 28th at 5PM EST, the GitHub Service Team will take the GitHub Enterprise service down to apply the 3.9.5 hotpatch which, among a handful of other changes outlined below, addresses the cause of the failure which prevented the previous upgrade from completing.

In light of the recent network difficulties faced by campus, this upgrade is being scheduled further in the week to ensure sufficient notice is provided. Under normal circumstances (and outside major holidays and university closures), GitHub Enterprise upgrades are nearly always scheduled on Mondays for consistency and continuity reasons.

Some changes have been omitted from this list due to their relevance to the NC State GitHub Enterprise instance, but you can look at the full 3.9.5 release notes for a complete changelog.

Security fixes

  • Packages have been updated to the latest security versions.

Bug fixes

  • On an instance with GitHub Actions enabled, scale sets configured at the enterprise level did not appear for use within the instance’s organizations or repositories.
  • On an instance with a GitHub Advanced Security license and secret scanning enabled, secret scanning alerts could fail to show an error message in the UI when a failure occurred closing or reopening the alert.
  • On an instance with a GitHub Advanced Security license and secret scanning enabled, and when using Safari, changing additional match requirements for a custom pattern did not retrigger custom pattern evaluation against a user submitted test string.
  • On an instance with a GitHub Advanced Security license and secret scanning enabled, when token location(s) included a commit that introduced a large change, the page for viewing the alert would load slowly.
  • In some cases, users could reopen a pull request that should not have been able to be reopened.
  • When viewing fine-grained personal access tokens, the permissions text for pre-receive hooks was not visible for selection when filtering by permission.
  • On an instance with a GitHub Advanced Security license and secret scanning enabled, in some cases, custom patterns would erroneously show no results for a dry run.

Changes

  • On an instance with GitHub Actions enabled, the software on ephemeral runners is updated automatically.
  • When running async repository repairs, the output message about scheduling a repair job is more accurate.