Unable to use .Net 6.0 preview

[afucher]

Description:
I'm trying to update my project with the preview version of .NET 6, but when I try to set the version on setup-dotnet to 6 it doesn't find the version to download.

Task version:
actions/setup-dotnet@v1

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
My repo is private, but to reproduce just need to set the version to 6.0.0 or 6.0.0-preview.1

Expected behavior:
It should download the sdk and setup all the env.

Actual behavior:
It doesn't find the preview, and show this error:

dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.0-preview/dotnet-sdk-6.0.0-preview-linux-x64.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: Cannot download: https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.0-preview/dotnet-sdk-6.0.0-preview-linux-x64.tar.gz
dotnet-install: Downloading legacy link: https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.0-preview/dotnet-dev-ubuntu.18.04-x64.6.0.0-preview.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: Cannot download: https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.0-preview/dotnet-dev-ubuntu.18.04-x64.6.0.0-preview.tar.gz
dotnet_install: Error: Could not find/download: `.NET Core SDK` with version = 6.0.0-preview
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support

[blai30]

Specify the dotnet-version to be 6.0.100-preview.1.21103.13. This worked for me.

[JeroenBos]

For preview 2, specifying the dotnet-version to be 6.0.100-preview.2.21155.3 worked for me.

For any version, it's the sdk version from the release metadata.

[AraHaan]

Yep, I normally always even on stable do the exact version from the release metadata.

Although perhaps another option could be done: using a repository to simulate as if the specific software and versions the repository contains inside of a yaml file is default installed by the worker (CI) on the OS's that can be used with github actions.

That way setup-dotnet would only need to add it to the path and be done, and then that repository for the "worker" to simulate it would only need a pull request to update the software and it will be updated for everyone that "subscribes" to use that "worker extension".

So basically I would call it an github actions worker extension repository which would on the default branch make a new worker image (hosted by github and not self hosted), that just adds more software / more up to date software for it.

So then the workflow for it would be as follows:

• all commits to main tells github to rebuild that github hosted worker image (which is the path to the repository in the form of <username>/githubworkerext and only yml changes would regenerate the worker image)
• all commits to updates would be for updates (would later get squashed to a single commit to main for a single update every x days)
• all pull requests (except from updates) would need to be targeting updates to merge into.

This seems to be a better option to me tbh than either:

• having to manually install the software to the worker (or manually install the updates and download them)
• having to self host if you want the CI to get faster and ship by default with that specific software and version.

And yes the worker would basically be a separate "drive" that would be mounted to points as if that software and version came preinstalled on the worker and acts as an extension for the base image, so then the extension would not have to worry about OS updates, or software updates on the base default worker.

[LanceMcCarthy]

For preview3, this following works for me

    - name: Install .NET Core
      uses: actions/setup-dotnet@v1.7.2
      with:
        dotnet-version: '6.0.100-preview.3.21202.5'

[GGG-KILLER]

v1.8.0 has been released which includes #110.
Should resolve this by simply doing:

    - name: Install .NET Core
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: '6.0'
        include-prerelease: True

[AraHaan]

@GGG-KILLER in this case does this auto resolve to whatever the latest public 6.0 preview release to the .NET SDK is then?

[GGG-KILLER]

@GGG-KILLER in this case does this auto resolve to whatever the latest public 6.0 preview release to the .NET SDK is then?

Yes, it should

[vsafonkin]

Thank you @GGG-KILLER for his help! Closed.