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
->v4
v3.0.3
->v4.2.0
Release Notes
actions/checkout (actions/checkout)
v4
Compare Source
actions/setup-dotnet (actions/setup-dotnet)
v4.2.0
Compare Source
v4.1.0
Compare Source
What's Changed
Bug fixes :
isGhes
logic by @jww3 in https://github.com/actions/setup-dotnet/pull/556Dependency 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
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
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 https://github.com/dotnet/core/issues/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 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
cache
andcache-dependency-path
were added. Thecache
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:
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:
More details about the new syntax can be found here.
global-json-file
input was updated to accept absolute paths in https://github.com/actions/setup-dotnet/pull/396 by @othmane-kinane-nwglobal.json
was 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-action
by @JamesMGreene in https://github.com/actions/setup-dotnet/pull/348New Contributors
Full Changelog: actions/setup-dotnet@v3...v3.1.0
Configuration
📅 Schedule: Branch creation - "before 9am on Friday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.