Here is what you do if you receive messages like this:
Errors in packages.config projects
Unable to find version ‘9.0.171219’ of package ‘Sitecore.Kernel.NoReferences’.
https://sitecore.myget.org/F/sc-packages/api/v3/index.json: Unable to load the service index for source https://sitecore.myget.org/F/sc-packages/api/v3/index.json.
An error occurred while sending the request.
The remote name could not be resolved: ‘sitecore.myget.org’
Sitecore have been hosting NuGet packages on MyGet for a long time. But Sitecore have decided to move the package storage elsewhere. The move should have been executed November 2023, but because of MyGet service have been unstable, the decision have been accelerated.
This means that you need to update your build environment:
Old Url | New Url |
https://sitecore.myget.org/F/sc-packages/api/v3/index.json | https://nuget.sitecore.com/resources/v3/index.json |
https://sitecore.myget.org/gallery/sc-npm-packages | https://www.npmjs.com/ |
Furthermore, the artifact provider is now https://cloudsmith.io/~sitecore/repos/resources/groups/
HOW TO UPDATE NUGET
In your NuGet.config, make sure the packageSources points to nuget.sitecore.com:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<solution>
<add key="disableSourceControlIntegration" value="true" />
</solution>
<packageSources>
<clear />
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
<add key="Sitecore" value="https://nuget.sitecore.com/resources/v3/index.json" />
</packageSources>
</configuration>
MORE TO READ:
- KB1002999: Transition of Sitecore public feeds from MyGet to NuGet after November 2023 from Sitecore
- Should You Host Your Own Sitecore Feeds? from The Bits That Byte
- Is MyGet gone for good? from Reddit
- Sitecore MyGet repository access issue [closed] from Sitecore StackExchange
- Sitecore Moving From MyGet To Nuget For Public Feeds from Learn With Memes