Skip to content

chore(deps): update actions/setup-dotnet action to v5#39

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/actions-setup-dotnet-5.x
Open

chore(deps): update actions/setup-dotnet action to v5#39
renovate[bot] wants to merge 1 commit intomainfrom
renovate/actions-setup-dotnet-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 3, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/setup-dotnet action major v1 → v5
actions/setup-dotnet action major v3 → v5

Release Notes

actions/setup-dotnet (actions/setup-dotnet)

v5.2.0

Compare Source

v5.1.0

Compare Source

What's Changed
Documentation
Dependency updates
New Contributors

Full Changelog: actions/setup-dotnet@v5...v5.1.0

v5.0.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v5...v5.0.1

v5.0.0

Compare Source

What's Changed

Breaking Changes

Make sure your runner is updated to this version or newer to use this release. v2.327.1 Release Notes

Dependency Updates
Bug Fixes

New Contributors

Full Changelog: actions/setup-dotnet@v4...v5.0.0

v5

Compare Source

v4.3.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v4...v4.3.1

v4.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-dotnet@v4...v4.3.0

v4.2.0

Compare Source

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: actions/setup-dotnet@v4...v4.2.0

v4.1.0

Compare Source

What's Changed

Bug fixes :
Dependency updates :

New Contributors

Full Changelog: actions/setup-dotnet@v4...v4.1.0

v4.0.1

Compare Source

What's Changed

Documentation changes:
Dependency updates:

New Contributors

Full Changelog: actions/setup-dotnet@v4...v4.0.1

v4.0.0

Compare Source

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: actions/setup-dotnet@v3...v4.0.0

v4

Compare Source

v3.4.2

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v3...v3.4.2

v3.4.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v3...v3.4.1

v3.4.0

Compare Source

What's Changed
  • Update actions/cache to 4.0.3 by @​mahabaleshwars in #​620
    In scope of this release we updated actions/cache package to ensure continuous support and compatibility, as older versions of the package are now deprecated. For more information please refer to the toolkit/cache.
New Contributors

Full Changelog: actions/setup-dotnet@v3...v3.4.0

v3.3.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v3...v3.3.1

v3.3.0

Compare Source

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: actions/setup-dotnet@v3.2.0...v3.3.0

v3.2.0

Compare Source

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: actions/setup-dotnet@v3...v3.2.0

v3.1.0

Compare Source

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: actions/setup-dotnet@v3...v3.1.0

v3.0.3: Fix issue with ECONNRESET and refactor authutil

Compare Source

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)

v3.0.2: Updating @​action/core, adding logic for processing the DOTNET_INSTALL_DIR environment variable.

Compare Source

In the scope of this release such changes were made:

  1. The logic for processing the DOTNET_INSTALL_DIR environment variable was added to support relative paths and paths containing ~ #​332
  2. The version of @actions/core was bumped to 1.10.0 #​331

v3.0.1: Enable DOTNET_INSTALL_DIR environment variable

Compare Source

In scope of this release the DOTNET_INSTALL_DIR environment variable was enabled to add the ability to change the installation directory for .NET SDK #​329. The DOTNET_INSTALL_DIR can be helpful when access to the default installation directory, for instance, on self-hosted runners, is denied.

Example of usage:

build:
  runs-on: self-hosted
  env:
    DOTNET_INSTALL_DIR: "path/to/directory"
  steps:
    - uses: actions/setup-dotnet@v3
      with:
        dotnet-version: '3.1.x'

v3.0.0

Compare Source

This major release includes the following changes:

    - uses: actions/setup-dotnet@v3
      with:
        dotnet-version: '6.0.x'
        dotnet-quality: 'preview'
    - run: dotnet build <my project>

More in detail here.

  • #​241 The output variable dotnet-version which contains the installed by the action SDK version was added in #​324:
    - uses: actions/setup-dotnet@v3
      id: cp310
      with:
        dotnet-version: '3.1.422'
    - run: echo '${{ steps.cp310.outputs.dotnet-version }}' # outputs 3.1.422

More in detail here.

  • The dotnet-version syntax was updated and now it allows to specify the prerelease version without using include-prerelease input. The include-prerelease input was cut out:
    - uses: actions/setup-dotnet@v3
      with:
        dotnet-version: '5.0.0-preview.6'

More in detail here.

  • #​251 The problem with out of support .NET version warnings was solved in #​315.

Breaking changes:

  • Installation paths for Windows and Ubuntu images were changed to match the location of pre-installed SDKs. In more detail, read here.

v3

Compare Source

v2.2.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v2...v2.2.1

v2.2.0

Compare Source

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: actions/setup-dotnet@v2.1.1...v2.2.0

v2.1.1: Add support for Windows-arm

Compare Source

In scope of this release we add support for Windows-arm. Besides, we change getInput to getBooleanInput for include-prerelease.

v2.1.0: Package updates, support for global json file in a subdirectory, installer scripts updates

Compare Source

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

Compare Source

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.

v2

Compare Source

v1.10.1

Compare Source

What's Changed

Full Changelog: actions/setup-dotnet@v1...v1.10.1

v1.10.0

Compare Source

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: actions/setup-dotnet@v1.9.1...v1.10.0

v1.9.1: Installer scripts updates

Compare Source

Update dotnet-install scripts to the latest versions: #​270

v1.9.0: Support for installation of multiple versions, warnings for deprecated versions

Compare Source

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

v1.8.2: Package Updates, Improvement for global.json handling

Compare Source

  • Bump path-parse from 1.0.6 to 1.0.7 #​222
  • Update installer scripts #​226
  • Support rollForward option for global.json #​224

v1.8.1: Update packages

Compare Source

  • Bump ws from 7.3.1 to 7.5.0 #​212
  • Bump hosted-git-info from 2.8.8 to 2.8.9 #​198
  • Bump lodash from 4.17.20 to 4.17.21 #​197
  • Bump node-notifier from 8.0.0 to 8.0.1 #​158
  • Update installers scripts #​204

v1.8.0: Support of preview versions, input validation improvements and other bug fixes

Compare Source

This release includes the following PRs:

  • Add include-prerelease input to be able to match latest prerelease versions #​110
  • Support various nuget.config name formats #​188
  • Add workaround to fix BOM-related error during parsing global.json #​192
  • Improve key names validation from user' nuget config #​187
  • Fix for 5.x notation #​175

v1.7.2: Package Updates

Compare Source

Update @actions/core Version and move towards uses environment file

v1.7.1: Side-by-Side Installation

Compare Source

Bug fixes for DOTNET_ROOT and generic dotnet versions

v1.7.0: Side-by-Side Installation

Compare Source

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.

v1.6.0: License and documentation updates

Compare Source

Adding module licenses. Minor updates to scripts and documentation including readme examples to use main branch.

v1.5.0: Follow proxy settings and use wildcard for patch versions

Compare Source

Follows self-hosted runner proxy settings

Also introduces a wildcard for a patch version, allowing 3.1.x to install the latest release.

v1.4.0: Package Authentication and Process Updates

Compare Source

  • Removes use of obsolete .NET Core SDK releases endpoint
  • Dependency updates for packages
  • Improve documentation clarity
  • Adds NuGet package authentication set-up, documentation in README.md

v1.3.0

Compare Source

v1.2.1

Compare Source

v1.2.0: Deprecate version

Compare Source

Deprecate version

v1.1.0

Compare Source

Export dotnet_root

v1.0.2

Compare Source

Consume new toolkit

v1.0.1

Compare Source

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants