We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://dotnetcli.blob.core.windows.net/dotnet/Runtime/9.0/latest.version url is returning 9.0.0-rc.2.24473.5 instead of 9.0.0
Just open the provided Microsoft website url.
It should return the latest stable release number (9.0.0), just like https://dotnetcli.blob.core.windows.net/dotnet/Runtime/8.0/latest.version that returns 8.0.11
It returns 9.0.0-rc.2.24473.5
Works fine on .NET 8
I tried to workaround the cache (if any) by passing a random query string, but it didn't work
No response
The text was updated successfully, but these errors were encountered:
This belongs in dotnet/install-scripts. Possibly the same issue as #546
dotnet/install-scripts
Sorry, something went wrong.
@rbhanda @marcpopMSFT do you know what process might be missing here to update this?
working on this
This has been fixed. https://dotnetcli.blob.core.windows.net/dotnet/Runtime/9.0/latest.version returns 9.0.0 now
Thank you very much!
No branches or pull requests
Description
https://dotnetcli.blob.core.windows.net/dotnet/Runtime/9.0/latest.version url is returning 9.0.0-rc.2.24473.5 instead of 9.0.0
Reproduction Steps
Just open the provided Microsoft website url.
Expected behavior
It should return the latest stable release number (9.0.0), just like https://dotnetcli.blob.core.windows.net/dotnet/Runtime/8.0/latest.version that returns 8.0.11
Actual behavior
It returns 9.0.0-rc.2.24473.5
Regression?
Works fine on .NET 8
Known Workarounds
I tried to workaround the cache (if any) by passing a random query string, but it didn't work
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: