What’s new

• #3628 DirectX June 2010 on Visual Studio 2019
• #3634 NUnit Console 3.12.0
• #3635 Firefox 86.0.1
• #3636 PowerShell Core 7.1.3
• #3637 Google Chrome 89.0.4389.90
• #3638 Microsoft Edge 89.0.774.50
• #3639 CMake 3.19.6
• #3640 Visual Studio 2019 version 16.9.1
• #3641 Visual Studio 2019 version 16.10 Preview 1
• #3642 .NET SDK 3.1.407, .NET SDK 5.0.201, .NET SDK 6.0.100-preview.2
• #3644 Doxygen 1.9.1
• #3645 Go 1.16.2, 1.15.10, 1.14.15

Previous worker image

There is a build worker image available from previous deployment. You can use it in case of any issues with the current image:

Previous Visual Studio 2019

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2019

What’s new

• #3615 Qt 6.0.1
• #3618 Visual Studio 2019 version 16.8.5
• #3619 Visual Studio 2019 version 16.9 Preview 4
• #3620 CMake 3.19.4
• #3621 .NET Core 3.1.406
• #3622 Firefox 85.0.2
• #3623 Microsoft Edge 88.0.705.68
• #3624 Chrome 88.0.4324.96
• #3625 PowerShell Core 7.1.2
• #3626 DirectX SDK is not included into VS 2019 image anymore

Previous worker image

There is a build worker image available from previous deployment. You can use it in case of any issues with the current image:

Previous Visual Studio 2019

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2019

Node 14

Node.js 14.x is now default on Visual Studio 2019 image.

If your build is broken because of that change and you need to get back to Node 8 please add the following to appveyor.yml:

init:
- ps: Install-Product node 8

What’s new

• #3598 Ruby 3.0, Ruby 2.7.2
• #3599 Node.js 14 is default on Visual Studio 2019 image
• #3601 InnoSetup 6.1.2
• #3603 Visual Studio 2019 version 16.8.4
• #3604 CMake 3.19.2
• #3605 Firefox 84.0.2
• #3606 Node 15.6.0, 14.15.4, 12.20.1, 10.23.1
• #3607 Python 3.9.1, Python 3.8.7
• #3608 PowerShell Core 7.1.1

Previous worker image

There is a build worker image available from previous deployment. You can use it in case of any issues with the current image:

Previous Visual Studio 2019

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2019

What’s new in both macos and macos-mojave images

• Xcode 9.4.1
• Xcode 10.3
• Xcode 11.3.1
• XCode 11.7 (macOS image only)
• XCode 12.3 (macOS image only)
• Qt 6.0
• Qt 5.15.2
• Qt 5.14.2
• Qt 5.12.10
• PowerShell 7.1.0
• Homebrew 2.7.0
• .NET Core SDK 3.1.404
• .NET Core SDK 5.0.101
• Python 3.9.1
• Python 3.8.6
• Python 3.7.9
• Python 3.6.12
• Go 1.15.6
• Go 1.14.13
• Node.js 15.5.0
• Node.js 14.15.3
• Node.js 12.20.0
• CMake 3.19.2

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

• Previous macOS
• Previous macOS-Mojave

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous macos

What’s new in Ubuntu images

• Python 3.9.1
• Golang 1.14.13, 1.15.6
• .NET 5.0.101
• CMake 3.19.1
• Qt 6.0.0, 5.15.2
• Ubuntu 20.04: Doxygen 1.8.20
• Ubuntu 18.04: Doxygen 1.8.18
• Ubuntu 16.04: Doxygen 1.8.17

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

• Previous Ubuntu
• Previous Ubuntu1604
• Previous Ubuntu1804
• Previous Ubuntu2004

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Ubuntu