GitHub Actions – macOS and Windows virtual environments updates

We’ve fully deployed several updates to the GitHub Actions virtual environments. Highlights include:

Windows Server 2016 R2

  • Added Android SDK Build Tools 29.0.0 and 29.0.2
  • Added Android SDK Platform 10 (API 29)
  • Upgraded Git 2.22.0 to 2.23.0
  • Added Go 1.13
  • Upgraded Rust 1.37.0 to 1.38.0
  • Upgraded Google Chrome 76.0.3809.100 to 77.0.3865.90
  • Upgraded Chrome Driver 76.0.3809.68 to 77.0.3865.40
  • Upgraded Mozilla Firefox 68.0.2 to 69.0.1
  • Upgraded Yarn 1.17.3 to 1.19.1
  • Downgraded npm 6.10.3 to 6.9.0
  • Added newer versions and removed older versions of .NET Core SDK and Runtime
  • Upgraded Typescript 3.5.3 to 3.6.3
  • Upgraded Azure CosmosDb Emulator 2.4.5.0 to 2.5.7.0
  • Upgraded jq-1.5 to jq-1.6
  • Upgraded Vcpkg 2019.08.16 to 2019.09.12

Windows Server 2019

  • Upgraded Rust 1.37.0 to 1.38.0
  • Upgraded Google Chrome 76.0.3809.132 to 77.0.3865.90
  • Upgraded Chrome Driver 76.0.3809.132 to 77.0.3865.40
  • Upgraded Yarn 1.17.3 to 1.19.1
  • Added newer versions and removed older versions of .NET Core SDK and Runtime
  • Upgraded Azure CosmosDb Emulator 2.5.6.0 to 2.5.7.0

macOS 10.14

  • Note: Xcode 11.1 will be set as the default in a coming update
  • Upgraded Ruby 2.6.4 to 2.6.5
  • Added pip 19.2.3 (Python 3.7)
  • Upgraded fastlane 2.132.0 to 2.133.0
  • Added Xcode 11.2_beta 2
  • Added Xamarin.iOS SDK 13.4.0.2
  • Added Xamarin.Mac SDK 6.4.0.2

GitHub Actions is changing how we evaluate some events in order to make sure we always run workflows from known refs in your repository. Going forward the following events will use the workflow from the repository’s default branch instead of the SHA of the event.

  • status
  • check_run
  • check_suite
  • page_build

We’ve removed support for the commit_comment event.

If your workflow uses the actions/checkout action you will now get the code from the default branch instead of the SHA in the event. Variables like GITHUB_REF and GITHUB_SHA will now have the default ref and SHA. This will cause your workflow to behave differently and potentially break if you rely on the specific version of the code at that SHA. The SHA for the event will still be included in the event payload if you need to access it.

See more