Fix encoding issue in feed url with possible prerelease package versions (for example 1.1.0+2). When promoting packages with the "+" character, a 404 error occurred (not found). Click for details
Removed dependency on .nuspec XML namespace described in detail in this Pull Request
All credits go to Shad Storhaug for all his hard work on this
7-19-2019
Major update for Promotion of multiple packages in one go (by specifying the package ids separated by semicolons) described in detail in this Pull Request
All credits go to Shad Storhaug for all his hard work on this
Changed this update to a major update (2.x) and reverted to old version for the 1.x update
11-06-2019
Reverted to older version because of Bug.
28-05-2019
Added ability to select only packages in local feed (fix issue #19)
Fixed an issue when versions contain semver 2.0 compatible parts (e.g. 1.0.19133.1-beta+master.69f88edb)
Thanks Michael Zehnder!
11-02-2019
Bug in running the task in Release Management due to url
07-02-2019
Accounts natively created in Azure DevOps (dev.azure.com) threw an error when promoting the package (fix issue #16)
Added Support for Pyhton, Maven and Universal Packages
Added a Local Test Runner to test easily
10-01-2019
The feed, package and view to promote can now be specified via variables (thanks dhuessmann)
02-01-2019
Fixed an issue with editable package version (thanks dhuessmann)
18-05-2017
Added: Initial preview release
Description
BEWARE: This task does not work for on-prem TFS / Azure DevOps Server
This task enables you to promote a package in VSTS Package Management to a specific Release View. You can use Release Views to communicate Package Quality as described here.
In this task, you select the package feed from your account, the package, the version and the Release View to which you want to promote your package.
Supports NuGet and NPM
Find the task in the Utility category of Build
Known issues
No support for other feedTypes than NuGet and npm
Documentation
This task was inspired by a blogpost that I wrote for promoting a package to a Release View
Please check the Wiki (coming soon).
If you have ideas or improvements, don't hestitate to leave feedback or file an issue.
