-
Notifications
You must be signed in to change notification settings - Fork 482
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.
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
setup-dotnet in version 1.7.0 no longer works correctly for channel versions, such as 3.1 or 3.1.x #128
Comments
Breaks all my deployment scripts. Considering that the "basic" sample in the readme file now is broken, there are probably hundreds or thousands of people with broken scripts. This should probably be fixed or reverted to the prior version immediately. from readme:
|
Confirming all of our deployments are also broken now, commits this morning worked but latest ones failing. |
We've experienced this issue breaking the Actions provided by Microsoft Azure to deploy webapps depend on DOTNET_ROOT being set. This also breaks version requests in the style We've hotfixed by rolling back to v1.6.0. |
Looks like the We got our builds running but removing this action BUT are no longer getting annotations generated from the cli output. Would love a patch asap ref: |
The current version (1.7.0) fails to install our required versions correctly (see actions/setup-dotnet#128). Pinning to the previous release until that gets fixed.
Well, not requiring this action unless you need a different version of the dotnet cli... |
I've reverted the tag update for v1 back to 1.6.0 and will investigate. |
Description
setup-dotnet
in version 1.7.0 no longer works correctly for channel versions, such as3.1
or3.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
Example yaml file can be found here. Replacing
@v1
(which points to1.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.
The text was updated successfully, but these errors were encountered: