(maint) Update actions/setup-dotnet action to v5 #73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/actions-setup-dotnet-5.x
branch
from
1cd8e27 to
5633967
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-dotnet-5.x
branch
from
5633967 to
bb6adb5
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-dotnet-5.x
branch
from
bb6adb5 to
5b19336
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-dotnet-5.x
branch
from
5b19336 to
ad824d2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.4.2→v5.0.1Release Notes
actions/setup-dotnet (actions/setup-dotnet)
v5.0.1Compare Source
What's Changed
Full Changelog: actions/setup-dotnet@v5...v5.0.1
v5.0.0Compare 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
v4.3.1Compare Source
What's Changed
v4- Removeazureedge.netfallback logic and update install scripts by @zaataylor in #572As outlined in Critical .NET Install Links Are Changing, remove the storage account fallback logic added for v4 in #566 and update the install scripts accordingly.
Related issue: dotnet/install-scripts#559
Full Changelog: actions/setup-dotnet@v4...v4.3.1
v4.3.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-dotnet@v4...v4.3.0
v4.2.0Compare 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.0Compare Source
What's Changed
Bug fixes :
isGheslogic by @jww3 in #556Dependency updates :
New Contributors
Full Changelog: actions/setup-dotnet@v4...v4.1.0
v4.0.1Compare Source
What's Changed
Documentation changes:
Dependency updates:
New Contributors
Full Changelog: actions/setup-dotnet@v4...v4.0.1
v4.0.0Compare 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
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
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.