Repackage Package
  • 30 May 2024
  • 2 Minutes to read
  • Dark
  • PDF

Repackage Package

  • Dark
  • PDF

Article summary

The Repackaging API is available as both a pgutil command and an HTTP Request, and provides the programmatic ability to repackage prerelease packages by posting JSON-encoded or Form-encoded data.

⚠ The Repackaging API is available in paid and trial ProGet editions, and will raise a 500 in free editions.

🚀 Quick Example: Repackaging a NuGet package with pgutil

This example will repackage myNugetPackage version 4.3.2-rc.1 to 4.3.2 in the feed myNugetFeed

pgutil packages repackage --feed=myNugetFeed --package=myNugetPackage --version=4.3.2-rc.1 --new-version=4.3.2

This API requires ProGet 2023.0 or later.

Command Specification (CLI)

The packages repackage command set is used to repackage a package to a package with a different version.

The --package and --version options are always required, and the --qualifier option is required for multifile packages like Debian and RubyGems.

Repackaging a NuGet Package requires the feed (e.g. myNugetFeed), name (e.g. myNugetPackage) current version (e.g. 1.0.0-rc.1) and new version (e.g. 1.0.0):

pgutil packages repackage --feed=myNugetFeed --package=myNugetPackage --version=1.0.0-rc.1 --new-version=1.0.0

Repackaging an npm Package requires the feed (e.g. MyNpmFeed), name (e.g. myNpmPackage), scope (e.g. myScope), current version (e.g. 2.0.0-rc.1) and new version (e.g. 2.0.0):

pgutil packages repackage --feed=MyNpmFeed --package=@myScope/myNpmPackage --version=2.0.0-rc.1 --new-version=2.0.0

Note source options must also be specified unless you have the "Default" source configured, and that a feed may be instead specified in the source. See Working with Sources to learn more.

HTTP Request Specification

To promote a package, simply POST to the URL with an appropriate API Key and JSON object as the body with the following properties:

feed*Name of the feed where the target package is located
groupGroup-portion of the package's name; this is only applicable for Universal Packages
name*Name of the target package
version*Version of the target package
newVersion*Version of the new package to create
commentsComments to append to repackaging audit history
toFeedWhen specified, promotes the package to the specified feed instead of keeping it in feed.

* required property.

Previous versions of ProGet used groupName and packageName instead of group and name; these may still be used, but aren't recommended.

As JSON-encoded data:

POST /api/repackaging/repackage

Content-Type: application/json

  "feed": "myFeed",
  "name": "myPackage",
  "version": "4.3.2-rc.1",
  "newVersion": "4.3.2",
  "comments": "This package was repackaged by an automated process."

As Form-encoded data:

POST /api/repackaging/repackage

Content-Type: application/x-www-form-urlencoded


HTTP Response Specification

200 (Success)creates a new package in the same feed, ortoFeed when specified.
400 (Invalid Input)indicates invalid or missing properties on the package; the body will provide some details as text
403 (Unauthorized API Key)indicates a missing, unknown, or unauthorized API Key
500 (Server Error)indicates an unexpected error; the body will contain the message and stack trace, and this will also be logged

Was this article helpful?