ProGet 5.0.13 Has Been Released

We just shipped ProGet 5.0.13. It's a maintenance release of ProGet 5.0 which means that there is minimal risk to upgrading from an earlier 5.0. However, if you're planning to upgrade from a version prior to 5.0, make sure to read the appropriate upgrade notes.

To install or upgrade, simply download ProGet and run the installer.

Here's what we changed between 5.0.12 and 5.0.13:

  • PG-1293 - Change user caching so that any non-built-in directory user is cached regardless of whether Integrated Windows Authentication is enabled or not
  • PG-1292 - FIX: ruby, visx, Maven feeds do not record package deployments
  • PG-1291 - FIX: Connector packages are reordered when searching NPM feeds.
  • PG-1290 - FIX: NuGet packages may have an incorrect IsLatestVersion property on feeds with connectors.
  • PG-1289 - FIX: npm feeds do not record package deployments
  • PG-1288 - FIX: NuGet packages cannot be downloaded using a SemVer2 version number that includes build metadata
  • PG-1287 - FIX: Symbol server endpoints ignore feed-scoped privileges for corresponding NuGet feeds
  • PG-1286 - FIX: NPM packages may have no version tagged "latest".
  • PG-1285 - FIX: NuGet feeds show SemVer2 build metadata (text after +) in package display names
  • PG-1284 - Support package-ids endpoint in NuGet feeds
  • PG-1283 - FIX: Cannot delete semver2-compatible NuGet feed if there are symbols indexed
  • PG-1282 - Display a message on the Feed Replication page if trying to configure it when it is not supported by the current license key

To learn more about how we distinguish between major, minor, and maintenance releases, make sure to check out KB#1059 - When should I update?