setup-dotnet in version 1.7.0 no longer works correctly for channel versions, such as 3.1 or 3.1.x
See original GitHub issueDescription
setup-dotnet
in version 1.7.0 no longer works correctly for channel versions, such as 3.1
or 3.1.x
(which is interpreted the same).
Details
This is a regression. Version 1.6.0 is working fine. Example log output can be found here
Run actions/setup-dotnet@v1
with:
dotnet-version: 3.1
env:
CONFIGURATION: Release
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_NOLOGO: 1
DOTNET_SDK_VERSION: 3.1
NET_CORE_VERSION: netcoreapp3.1
NET_FRAMEWORK_VERSION: net48
NODE_JS_VERSION: 12
STEAM_TOKEN_DUMPER_NAME: ArchiSteamFarm.OfficialPlugins.SteamTokenDumper
STEAM_TOKEN_DUMPER_TOKEN: ***
/Users/runner/work/_actions/actions/setup-dotnet/v1/externals/install-dotnet.sh --version 3.1
dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1/dotnet-sdk-3.1-osx-x64.tar.gz
curl: (22) The requested URL returned error: 404 Not Found
dotnet-install: Cannot download: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1/dotnet-sdk-3.1-osx-x64.tar.gz
dotnet-install: Downloading legacy link: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1/dotnet-dev-osx-x64.3.1.tar.gz
curl: (22) The requested URL returned error: 404 Not Found
dotnet-install: Cannot download: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1/dotnet-dev-osx-x64.3.1.tar.gz
dotnet_install: Error: Could not find/download: `.NET Core SDK` with version = 3.1
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
##[error]The process '/Users/runner/work/_actions/actions/setup-dotnet/v1/externals/install-dotnet.sh' failed with exit code 1
Example yaml file can be found here. Replacing @v1
(which points to 1.7.0
as of today) with @v1.6.0
fixes the issue, as can be verified here.
Let me know if you need more info. Judging from how easily it regressed in my setup, I believe there shouldn’t be too much trouble localizing the culprit. Thank you in advance for your interest.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:21
- Comments:6 (1 by maintainers)
Top Results From Across the Web
GitHub BuildPipeline for Dotnet Core on Linux fails without ...
I tried to add changes to my code and the build pipeline for Linux stopped working. The ones for Windows and ...
Read more >How Do I Get .NET Preview Versions in GitHub Actions?
I wanted to setup a GitHub Action to build and test a .NET Preview project. Come in to read about how you can...
Read more >[Users] Unable to finish AIO 3.3.0 - VDSM - Ovirt List Archives
... trouble with the AIO = 3.3.0 install on Fedora 19 using <a href=3D"http://community.redhat.com/up-= and-running-with-ovirt-3-3/">jbrooks ...
Read more >Asp.net core 2.2 project is crashing on startup after updating ...
The asp.net core application was working properly (Version 16.5.5) before the Visual Studio update and now in it crashes in the startup when...
Read more >Getting Started with GitHub Actions for .NET Developers
GitHub actions are an easy way to automate common software workflows, such as performing checks and running tests when pull requests (PRs) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Confirming all of our deployments are also broken now, commits this morning worked but latest ones failing.
We’ve experienced this issue breaking the
${{ env.DOTNET_ROOT }}
environment environment variable in Github Actions. The variable is either set empty or not set at all.Actions provided by Microsoft Azure to deploy webapps depend on DOTNET_ROOT being set.
This also breaks version requests in the style
dotnet-version: 3.1.x
, which have to be hard pegged to a version.We’ve hotfixed by rolling back to v1.6.0.