Blog myget Nuget Sitecore
Ketan Sachan  

Sitecore’s Public Feed Shift: Embrace the Future of Package Management!

Introduction:

Sitecore developers, there’s a significant change on the horizon! The long-standing public feed provider, MyGet, has recently encountered some challenges, leaving its future uncertain. As a result, Sitecore has taken a proactive approach by transitioning to a new public feed provider, NuGet. This move promises to streamline package management and ensure a seamless experience for all developers.

In this blog, we’ll dive into the details of the transition and provide you with a comprehensive guide to adapt your workflows for the new Sitecore public feeds.

A Smooth Transition to NuGet:

On November 30, 2023, Sitecore officially completed its transition from MyGet to the new provider, NuGet. Now, you can access Sitecore packages through the following URL: https://nuget.sitecore.com/resources/v3/index.json . Additionally, Sitecore’s custom NPM feed has moved to the public NPM provider at https://www.npmjs.com/ , simplifying the package retrieval process.

Embracing the Advantages:

By making this shift, Sitecore aims to offer several benefits to its dedicated developers and partners:

  1. Unwavering Reliability: NuGet is renowned for its reliability, ensuring consistent and stable access to Sitecore packages, unlike the recent MyGet outage.
  2. Continuous Support: Sitecore is committed to providing ongoing support for the NuGet public feed, guaranteeing a dependable and long-term solution.
  3. Enhanced CI/CD Processes: Embracing the new public feeds in your workflows guarantees smooth CI/CD processes, allowing you to maintain an efficient development cycle.
  4. Stability at Its Best: NuGet provides a proven and robust package management ecosystem, reducing the likelihood of encountering installation issues.

Taking Action:

To ensure a seamless transition and avoid any interruptions beyond November 30, 2023, Sitecore strongly recommends the following steps:

  1. Update CI/CD Processes: Waste no time in modifying your CI/CD processes and build scripts to incorporate the new NuGet public feed (https://nuget.sitecore.com/resources/v3/index.json ) for accessing Sitecore packages.
  2. Internal Artifact Provider: If you’re using the internal artifact provider, remember to update the URL to the new location: https://cloudsmith.io/~sitecore/repos/resources/groups/.
  3. Custom NPM Feed: For those who relied on the custom NPM feed on MyGet, make a seamless switch to the public NPM provider, https://www.npmjs.com/ , to continue accessing Sitecore NPM packages.
  4. Package Availability: Certain packages, such as Sitecore Experience Commerce (10.3, 10.2, 10.1, and 10.0 are available), Content Hub, Sitecore PowerShell, and Sitecore Installation Framework, are not yet available through the public feeds. Stay informed through Sitecore’s updates on their availability.

Embrace the Future:

The transition from MyGet to NuGet presents a unique opportunity for Sitecore developers to embrace the future of package management. With NuGet’s reliable support, stable ecosystem, and streamlined processes, you can focus on what matters most: building exceptional Sitecore projects.

Sitecore is committed to enhancing the developer experience, and by staying informed, you can take full advantage of the evolving ecosystem. If you’ve faced challenges with MyGet, don’t hesitate to make the switch and embrace the new opportunities presented by Sitecore’s public feeds on NuGet!

For more information on this transition, visit: https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1002999. The future awaits, and together, we’ll create remarkable digital experiences with Sitecore!

Leave A Comment