Release metadata for 6.0.0-rc.1 has wrong release date set
See original GitHub issueThe [https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/6.0/releases.json][metadata] for the 6.0 SDKs has been updated to include the first RC release.
However, while the global latest-release-date
is set correctly (2021-09-14
), the entry for the 6.0.0-rc.1
release specifies release date
as 2021-11-25
.
It’s mostly harmless, but it’s likely also an easy fix.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
yarn install fails with `ENOENT: no such file or directory` ...
Running yarn install as part of a build step for a Docker image based on node:7 fails on Travis CI with ENOTEMPTY, EEXISTS...
Read more >ASP.NET Core updates in .NET 6 Release Candidate 1
NET 6 Release Candidate 1 (RC1) is now available and includes many great new improvements to ASP.NET Core. Here's what's new in this...
Read more >Restore code produces inconsistent timestamps/permissions
This issue is still partially present in v0.9.4. I was able to reproduce the timestamp mismatch, but not the permissions one.
Read more >ASP.NET Core updates in .NET 6 Release Candidate 2
NET 6 Release Candidate 2 (RC2) is now available. .NET 6 RC2 is very close to the final build of .NET 6 that...
Read more >Release Notes — llvmlite 0.39.0rc1-dirty documentation
This release predominantly adds new features and improves functionality. It's now possible to directly set LLVM metadata on global variables ...
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 FreeTop 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
Top GitHub Comments
@joeloff @sfoslund This issue is now fixed.
Thanks! Closing this issue.