Releases: actions/setup-dotnet
Package updates, support for global json file in a subdirectory, installer scripts updates
This release includes the following PRs:
-
Adding support for the
global-json-file
input: #276
Example of usage:- uses: actions/setup-dotnet@v2 with: global-json-file: csharp/global.json - run: dotnet build <my project> working-directory: csharp
-
Update @zeit/ncc to @vercel/ncc: #290
-
Update vulnerable packages: #289
-
Improve documentation and update installer scripts to the latest version: #278
v2.0.0
In scope of this release we changed version of the runtime Node.js for the setup-dotnet action and updated package-lock.json file to v2.
Breaking Changes
With the update to Node 16 in #271 all scripts will now be run with Node 16 rather than Node 12.
Installer scripts updates
Update dotnet-install scripts to the latest versions: #270
Support for installation of multiple versions, warnings for deprecated versions
This release includes the following PRs:
- Adding support to install multiple .NET versions in single action invocation: #240
example:
- uses: actions/setup-dotnet@v1
with:
dotnet-version: |
3.1.x
5.0.x
The latest installed .NET version is default, according .NET documentation.
- Adding the build warnings if the deprecated .NET versions are installed by action: #245
Package Updates, Improvement for global.json handling
Update packages
Support of preview versions, input validation improvements and other bug fixes
This release includes the following PRs:
Package Updates
Update @actions/core
Version and move towards uses environment file
Side-by-Side Installation
Bug fixes for DOTNET_ROOT and generic dotnet versions
Side-by-Side Installation
Allow side-by-side installation of multiple versions of dotnet. Also, also uses the preinstalled versions of dotnet on virtual-environments.
Bug fix for nuget.config file and various package updates.