.NET 6 SDK latest version endpoint returns incorrect version
See original GitHub issueMy apologies if this isn’t the correct place to raise this issue.
Describe the bug
.NET 6 SDK latest version endpoint isn’t outputting the correct version
To Reproduce
Go to https://dotnetcli.azureedge.net/dotnet/Sdk/6.0/latest.version
Currently shows 6.0.113
. The latest version should be 6.0.405
(at time of writing).
We use this endpoint to keep our own custom build containers up to date with the latest SDK patches through nightly updates. This came to light because we configured a minimal version of 6.0.201
on our project’s global.json
Issue Analytics
- State:
- Created 8 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
NETSDK1045: The current .NET SDK does not support ...
This error occurs when the build tools can't find the version of the .NET SDK that's needed to build a project. This is...
Read more >.NET 6 app fails to start because wrong SDK version on ...
First, I installed dotnet-runtime-7.0 (7.0.8 to be specific). I've got the same error. DLL was compiled with the latest SDK. The same version...
Read more >UnsupportedApiVersion error when giving some different ...
The versioning endpoint matcher policy invalidates any valid candidate by API version. This should be the last step and constraint.
Read more >Get App Version in .NET Core
We can define versions on our .NET Core applications, but how to get the version at runtime? There are several ways to do...
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 Free
Top 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
dotnet/Sdk/6.0/latest.version is different from what’s presented in the releases.json.
@rbhanda or @dcwhittaker - can you please take a look?
Thank you for resolving the issue!