Skip to content

Update actions/setup-dotnet action to v5#611

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

Update actions/setup-dotnet action to v5#611
renovate[bot] wants to merge 1 commit into
nextfrom
renovate/actions-setup-dotnet-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 8, 2026

This PR contains the following updates:

Package Type Update Change
actions/setup-dotnet action major v3v5

Release Notes

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

v5.3.0

Compare Source

What's Changed
Enhancements
Dependency Updates
Bug Fixes
New Contributors

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

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


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 this update 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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants