Skip to content

Update actions/setup-dotnet action to v4 #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
Turnerj merged 1 commit into from
Dec 26, 2024
Merged

Update actions/setup-dotnet action to v4 #24

Turnerj merged 1 commit into from
Dec 26, 2024

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/setup-dotnet action major v1.9.0 -> v4.1.0

Release Notes

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

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 https://github.com/actions/setup-dotnet/pull/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

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 @​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 (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:

  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.

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 https://github.com/dotnet/core/issues/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.

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 https://github.com/dotnet/core/issues/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

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 is behind base branch, 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.

@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from b9ed2d7 to aa97baf Compare July 9, 2024 16:57
@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from aa97baf to 80a6e03 Compare October 24, 2024 16:27
@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch 2 times, most recently from 7badca8 to f372634 Compare December 26, 2024 21:14
@renovate renovate bot force-pushed the renovate/actions-setup-dotnet-4.x branch from f372634 to 44015e3 Compare December 26, 2024 21:15
@Turnerj Turnerj merged commit 84cefc2 into main Dec 26, 2024
8 checks passed
@Turnerj Turnerj deleted the renovate/actions-setup-dotnet-4.x branch December 26, 2024 22:12
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

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Turnerj