chore(deps): update actions/setup-dotnet action to v4 #485
Conversation
This file contains 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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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:
v2.1.0->v4.0.0Release Notes
actions/setup-dotnet (actions/setup-dotnet)
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
Update Node.js runtime to version 20 by @harithavattikuti in #484
Non-breaking changes
setup-dotnet@v3 used to overwrite dotnet executable on each action run, which was causing action to fail on some occasions due to executable being still in use. In setup-dotnet@v4 we solved this issue by adding another install-script run that installs LTS version of dotnet executable and uses it for all subsequent dotnet installations. The first install-script run conducts the actual download only once per workflow.
New Contributors
Full Changelog: actions/setup-dotnet@v3...v4.0.0
v3.2.0Compare Source
What's Changed
In scope of this minor release, the ability to cache the NuGet
global-packagesfolder was added in https://github.com/actions/setup-dotnet/pull/303 by @nogic1008For 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
cacheandcache-dependency-pathwere added. Thecacheinput is optional, and caching is turned off by default,cache-dependency-pathis used to specify the path to a dependency file -packages.lock.json.Example of use-case:
More details can be found in the action's documentation.
Full Changelog: actions/setup-dotnet@v3...v3.2.0
v3.1.0Compare Source
What's Changed
This minor release includes the following new features:
More details about the new syntax can be found here.
global-json-fileinput was updated to accept absolute paths in https://github.com/actions/setup-dotnet/pull/396 by @othmane-kinane-nwglobal.jsonwas not found in the root directory was added in https://github.com/actions/setup-dotnet/pull/344 by @teo-tsirpanisIt also contains several infrastructure changes:
actions/publish-actionby @JamesMGreene in https://github.com/actions/setup-dotnet/pull/348New Contributors
Full Changelog: actions/setup-dotnet@v3...v3.1.0
v3.0.3: Fix issue with ECONNRESET and refactor authutilCompare 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 (https://github.com/actions/setup-dotnet/pull/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:
DOTNET_INSTALL_DIRenvironment variable was added to support relative paths and paths containing~#332@actions/corewas bumped to 1.10.0 #331v3.0.1: Enable DOTNET_INSTALL_DIR environment variableCompare Source
In scope of this release the
DOTNET_INSTALL_DIRenvironment variable was enabled to add the ability to change the installation directory for .NET SDK #329. TheDOTNET_INSTALL_DIRcan be helpful when access to the default installation directory, for instance, on self-hosted runners, is denied.Example of usage:
v3.0.0Compare Source
This major release includes the following changes:
dotnet-qualitywas added in #315:More in detail here.
dotnet-versionwhich contains the installed by the action SDK version was added in #324:More in detail here.
dotnet-versionsyntax was updated and now it allows to specify the prerelease version without usinginclude-prereleaseinput. Theinclude-prereleaseinput was cut out:More in detail here.
Breaking changes:
v2.1.1: Add support for Windows-armCompare Source
In scope of this release we add support for Windows-arm. Besides, we change getInput to getBooleanInput for include-prerelease.
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 has been generated by Mend Renovate. View repository job log here.