Sourced from actions/setup-dotnet's releases.
v4.0.0
What's Changed
In the scope of this release, the version of the Node.js runtime was updated to 20. The majority of dependencies were updated to the latest versions. From now on, the code for the setup-dotnet will run on Node.js 20 instead of Node.js 16.
Breaking changes
Update Node.js runtime to version 20 by
@harithavattikuti
in #484Non-breaking changes
- Refactor installer by
@nikolai-laevskii
in actions/setup-dotnet#432- Allow json comments by
@nikolai-laevskii
in actions/setup-dotnet#431- Sequential version install fix by
@nikolai-laevskii
in actions/setup-dotnet#433 setup-dotnet@v3 used to overwrite dotnet executable on each action run, which was causing action to fail on some occasions due to executable being still in use. In setup-dotnet@v4 we solved this issue by adding another install-script run that installs LTS version of dotnet executable and uses it for all subsequent dotnet installations. The first install-script run conducts the actual download only once per workflow.- Update fast-xml-parser and dotnet installer scripts by
@IvanZosimov
in actions/setup-dotnet#437- Update dependencies by
@IvanZosimov
in actions/setup-dotnet#440- Bump word-wrap from 1.2.3 to 1.2.4 by
@dependabot
in actions/setup-dotnet#444- Update installers by
@nikolai-laevskii
in actions/setup-dotnet#462- Update semver by
@dmitry-shibanov
in actions/setup-dotnet#468New Contributors
@HarithaVattikuti
made their first contribution in actions/setup-dotnet#484Full Changelog: https://github.com/actions/setup-dotnet/compare/v3...v4.0.0
v3.2.0
What's Changed
In scope of this minor release, the ability to cache the NuGet
global-packages
folder was added in actions/setup-dotnet#303 by@nogic1008
For caching, the action uses the
@toolkit/cache
library under the hood, which in turn allows getting rid of configuring the@actions/cache
action separately.Such input parameters as
cache
andcache-dependency-path
were added. Thecache
input is optional, and caching is turned off by default,cache-dependency-path
is used to specify the path to a dependency file -packages.lock.json
.Example of use-case:
- uses: actions/setup-dotnet@v3 with: dotnet-version: 6.x cache: true cache-dependency-path: subdir/packages.lock.json
More details can be found in the action's documentation.
Full Changelog: https://github.com/actions/setup-dotnet/compare/v3...v3.2.0
v3.1.0
What's Changed
... (truncated)
4d6c8fc
Upgrade Node to v20 (#484)2216f56
Update semver (#468)736bc6d
Merge pull request #462
from akv-platform/update-installersf5526c2
Update installers4dba25f
Bump word-wrap from 1.2.3 to 1.2.4 (#444)ada8800
Bump semver from 6.3.0 to 6.3.1 (#443)e174912
Update dependencies (#440)a6be55a
Update fast-xml-parser and dotnet installer scripts (#437)9b40770
Merge pull request #433
from akv-platform/sequential-version-install-fix4827734
Reduce number of e2e tests