Skip to content

Releases: actions/setup-dotnet

v4.2.0

26 Dec 22:43
87b7050
Compare
Choose a tag to compare

What's Changed

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow dotnet/core#9671.

New Contributors

Full Changelog: v4...v4.2.0

v3.3.0

26 Dec 21:46
ea9897a
Compare
Choose a tag to compare

What's Changed

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow dotnet/core#9671.

Full Changelog: v3.2.0...v3.3.0

v2.2.0

26 Dec 21:03
aab9aab
Compare
Choose a tag to compare

What's Changed

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow dotnet/core#9671.

Full Changelog: v2.1.1...v2.2.0

v1.10.0

26 Dec 20:16
71a4fd9
Compare
Choose a tag to compare

What's Changed

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow dotnet/core#9671.

Full Changelog: v1.9.1...v1.10.0

v4.1.0

24 Oct 14:03
3e891b0
Compare
Choose a tag to compare

What's Changed

  • Add workflow file for publishing releases to immutable action package by @Jcambass in #548
  • Upgrade IA Publish by @Jcambass in #550

Bug fixes :

Dependency updates :

New Contributors

Full Changelog: v4...v4.1.0

v4.0.1

09 Jul 14:31
6bd8b7f
Compare
Choose a tag to compare

What's Changed

Documentation changes:

Dependency updates:

New Contributors

Full Changelog: v4...v4.0.1

v4.0.0

04 Dec 14:24
4d6c8fc
Compare
Choose a tag to compare

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 #484
  • Sequential version install fix by @nikolai-laevskii in #433
    In setup-dotnet@v3, the dotnet executable was overwritten during each action run, sometimes leading to failures if the executable was still in use. This issue was resolved in setup-dotnet@v4 by introducing an additional install-script run that installs the LTS version of the dotnet executable and utilizes it for all subsequent dotnet installations. The actual download is performed only once per workflow by the initial install-script run. To use older versions, utilize global.json. For more details, refer to the documentation.

Non-breaking changes

New Contributors

Full Changelog: v3...v4.0.0

v3.2.0

29 May 11:43
3447fd6
Compare
Choose a tag to compare

What's Changed

In scope of this minor release, the ability to cache the NuGet global-packages folder was added in #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 and cache-dependency-path were added. The cache 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: v3...v3.2.0

v3.1.0

25 May 12:07
aa983c5
Compare
Choose a tag to compare

What's Changed

This minor release includes the following new features:

- uses: actions/setup-dotnet@v3
  with:
    dotnet-version: '7.0.2xx'

More details about the new syntax can be found here.

It also contains several infrastructure changes:

New Contributors

Full Changelog: v3...v3.1.0

Fix issue with ECONNRESET and refactor authutil

27 Oct 13:09
607fce5
Compare
Choose a tag to compare

In scope of this release we updated the link to the .Net Core releases index file (#337) in order to fix the ECONNRESET error. Besides, we refactored authutil.ts to get rid of xmlbuilder (#336)