Closed Gordonby closed 2 years ago
Hi @Gordonby We rely on this list for fetching the version, as the latest version here is 2.28.0 thats why the task is failing with 2.28.1. It generally takes around 1 week for latest versions to get updated everywhere.
Indeed, and running az upgrade
locally only retrieves 2.28.0.
I suppose if the user provided a version value that was in excess of the latest version, then it'd be nice if it actually went to the repo to try instead of relying on the outdated list.
I see that 2.29.0 has landed within a day of release. Perhaps the list you lean on for the version doesn't include smaller 0.0.1 releases.
Hi @Gordonby we looked into the above issue of 2.28.1 not being part of the list. So it was an expected behaviour and here is the response from azure cli team
Because 2.28.1 is a special version, it is only to solve the problems related to pip and does not want to affect other platforms, so it is not officially released to all platforms.
I guess that's why 2.28.1 doesn't appear in the list https://mcr.microsoft.com/v2/azure-cli/tags/list.
Also the list just isnt being used to verify a version but also make sure a docker image for that version is available so moving away from the list isnt easy. Adding support for edge builds should be able to help with the above issue so Ill take a look at it.
This issue is stale because it has been open for 7 days with no activity.
Hi @Gordonby I am closing this issue for now and will keep the Edge Build issue open https://github.com/Azure/cli/issues/53
Please reopen this if you feel this needs more information.
I'm getting the error
Error: Please enter a valid azure cli version. See available versions: https://github.com/Azure/azure-cli/releases.
When specifying
I get the error above. When I remove
azcliversion
the action installs version 2.28.0 of the Azure CLIv2.28.1 was released 3 days ago.![image](https://user-images.githubusercontent.com/17914476/136771741-8ccb449b-681b-4ec6-b059-b46f2383d612.png)