v1.10.1

What's Changed

• v1 - Remove dotnetcli.blob.core.windows.net storage account fallback logic and update install scripts by @zaataylor in #577
  As outlined in Critical .NET Install Links Are Changing, remove the storage account fallback logic added for v1 in #569 and update the install scripts accordingly.
  Related issue: dotnet/install-scripts#559

Full Changelog: v1...v1.10.1

v4.3.0

What's Changed

• README update - add permissions section by @benwells in #587
• Configure Dependabot settings by @HarithaVattikuti in #585
• Upgrade cache from 3.2.4 to 4.0.0 by @aparnajyothi-y in #586
• Upgrade actions/publish-immutable-action from 0.0.3 to 0.0.4 by @dependabot in #590
• Upgrade @actions/http-client from 2.2.1 to 2.2.3 by @dependabot in #592
• Upgrade undici from 5.28.4 to 5.28.5 by @dependabot in #596

New Contributors

• @benwells made their first contribution in #587
• @aparnajyothi-y made their first contribution in #586

Full Changelog: v4...v4.3.0

v4.2.0

What's Changed

• Enhance Workflows, Update Dependencies and Installer Scripts by @priyagupta108 in #555
• V4 - Use new .NET CDN URLs and update to latest install scripts by @heavymachinery in #566

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

• @priyagupta108 made their first contribution in #555
• @heavymachinery made their first contribution in #566

Full Changelog: v4...v4.2.0

v3.3.0

What's Changed

• V3 - Use new .NET CDN URLs and update to latest install scripts by @HarithaVattikuti in #567

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

What's Changed

• V2 - Use new .NET CDN URLs and update to latest install scripts by @HarithaVattikuti in #568

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

What's Changed

• V1 - Use new .NET CDN URLs and update to latest install scripts by @HarithaVattikuti in #569

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

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 :

• Fixed Basic Validation failure checks by @HarithaVattikuti in #545
• Revise isGhes logic by @jww3 in #556

Dependency updates :

• Bump fast-xml-parser from 4.3.6 to 4.4.1 by @dependabot in #540

New Contributors

• @Jcambass made their first contribution in #548
• @jww3 made their first contribution in #556

Full Changelog: v4...v4.1.0

v4.0.1

What's Changed

Documentation changes:

• Update README.md to use latest action version by @mikes-gh in #502
• Update links to runner software by @samuel-w in #499

Dependency updates:

• Bump undici from 5.27.2 to 5.28.3 by @dependabot in #515
• Bump braces from 3.0.2 to 3.0.3 and other dependency updates by @dependabot in #533

New Contributors

• @mikes-gh made their first contribution in #502
• @samuel-w made their first contribution in #499

Full Changelog: v4...v4.0.1

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 #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

• Refactor installer by @nikolai-laevskii in #432
• Allow json comments by @nikolai-laevskii in #431
• Update fast-xml-parser and dotnet installer scripts by @IvanZosimov in #437
• Update dependencies by @IvanZosimov in #440
• Bump word-wrap from 1.2.3 to 1.2.4 by @dependabot in #444
• Update installers by @nikolai-laevskii in #462
• Update semver by @dmitry-shibanov in #468

New Contributors

• @HarithaVattikuti made their first contribution in #484

Full Changelog: 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 #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