Roadmap: where ProGet has been, and where we see it going.

ProGet is by no means "feature complete", and although the software works great for our users today, we're actively working on making it even better. This roadmap page is a bit rough, but it should show you which changes we plan on making in releases to come.

We decide on what changes to make to ProGet based on a number of factors, the largest of which is user feature requests. If there's anything you think ProGet should do — or should do better — please contact us and let us know.

Version 5

The central theme of v5 is packaging your applications and components, so that you can ensure your software is built only once, and then deployed consistently across environments. This means not only hosting your developer libraries (such as NuGet, npm, etc.), but your Docker containers, universal packages, and romp packages as well.

To see specific planned changes, you can view our open ProGet issues in our issue tracker.

Already Released:

  • ProGet 5.1 - Docker Connectors, Virtual Packages, Inedo Hub Installer
  • ProGet 5.0 - Updated UI, Webhooks, File Browse, NuGet Feed support for SemVer2

ProGet 5.2 Plan:

Virtual connectors; these will allow you to connect one feed to another feed on the same instance of ProGet without using the UI; this will vastly speed up queries.

New Feed Types:

We plan to support these in the v5 line:

  • Support for Composer (PHP) packages
  • Support for PyPi (Python) Packages

Version 4

  • ProGet 4.8 - Asset Directories, Enhanced LDAP Directory
  • ProGet 4.7 - License Filtering, Support for Visual Studio Extensions (.vsix)
  • ProGet 4.6 - Vulnerability Scanning
  • ProGet 4.5 - Support for RubyGem repository
  • ProGet 4.4 - Package promotion, deployment records, and Linux
  • ProGet 4.3 - Docker repository support, SDK improvements
  • ProGet 4.2 - CDN/Cloud (S3, Azure) Package Storage
  • ProGet 4.1 - PowerShellGet support, multi-site replication across ProGet instances
  • ProGet 4.0 - Updated UI, Universal Feeds & Packages

The central theme of v4 was all about universal package management, which meant managing all of the various types of packages and feeds in the enterprise.

v4 is fully supported, fixes will continue to be shipped in the 4.8 release, and we will continue to maintain earlier v4 releases to resolve any critical or security issues discovered for users who cannot yet upgrade to 4.8.

Version 3

The central theme of v3 was to extend the reach of package serving to other registries/repositories including npm.

v3 is semi-retired, which means that we will provide very limited support to v3 users who have not yet upgraded, and will provide assistance in performing upgrades. However, we will no longer ship maintenance releases, patches, or other changes.

Version 2

The central theme of v2 was to introduced more filtering options (particularly for license types), and added meta-features such as the SDK, the API, and source code licensing.

v2 has been retired and is no longer supported.

Version 1

The initial release of ProGet provided basic NuGet feed support while introducing features such as connectors, filtering, multiple feeds, along with an integrated symbol & source server for NuGet packages.

v1 has been retired and is no longer supported.