NuGet
How to Use CI/CD Pipelines for Your NuGet Packages
Posted on January 8th, 2026.CI/CD for NuGet packages isn’t just a pain – it sometimes feels downright impossible.
CI/CD for NuGet packages isn’t just a pain – it sometimes feels downright impossible.
Versioning seems so simple – it’s just a number! But with NuGet, it’s anything but that. There are five distinct, multi-part version numbers that can be in a package, and each of these has its own formatting rules and behaviors.
If you work with CI/CD pipelines, artifact repositories, or DevOps workflows, you’ll be familiar with Amazon S3. It’s flexible and widely used, but as your repository grows, costs can add up fast. Storage is just one piece of it; request charges and egress fees can catch teams off guard, especially when traffic spikes. As you...
If you’re managing projects that rely on multiple teams delivering consistent components, you’ve probably noticed the chaos that comes from storing build artifacts and libraries in shared folders. Each team has its own way of organizing files, versions get mixed up, and no one really knows which asset the project should be using....
You’re likely pulling OSS packages straight from NuGet.org, npmjs.com, or PyPI.org, via the CLI. It’s the path of least resistance and the fastest way to get what your teams need. But without something sitting in the middle, it’s hard to know exactly what’s being pulled in or whether it meets your org’s requirements. When you pull OSS...
Internal registries are a smart way to manage OSS packages. They let you curate reusable code for your apps and cut down on risky repeat pulls from the wild. But when every team spins up its own siloed registry and tooling sprawls across the org, you end up with duplicate work, outdated packages, and security headaches that didn’t need...
Small delays, hidden dependencies, and tightly coupled systems can turn even minor updates into major headaches. Teams fall short of achieving what was intended as backlogs grow, urgent orders slip, and firefighting becomes the norm. Our latest webinar looks at these challenges through the story of LogistiCorp, a mid-sized...
Inedo’s newest whitepaper, “Migrating from Sonatype to ProGet“ releases this month, available both as a free PDF eBook, or as a series of articles on our blog. Migrating from Sonatype Nexus to ProGet is more than just copying your packages over. Nexus spreads its features across different products—Repository, Lifecycle,...
Many teams pull open-source packages into their projects without thinking twice. They might stash them locally, pass them around through CI pipelines, or build and test on their own. But without internal repositories or any guardrails in place, each team ends up working in its own bubble. That kind of flexibility can feel great at first,...
In ProGet 2025.14, we introduced two additional compliance rules to help you vet and monitor open-source packages in your organization. These are considered ProGet 2026 preview features, and represent our general roadmap focus for next year’s release: Software Composition Analysis (SCA) and security. In this article, we’ll...