trasloco

NuGetPackager@0 is retired: replace it with NuGetCommand@2

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
NuGetCommand@2
Kind of migration
manual migration
Automatic rewrite
No. This task needs a manual migration. trasloco modernize --check still finds the step.
Recommended action
Migrate this step manually to NuGetCommand@2 with the pack command.

Official sources

Last verified:

Why does my pipeline show a retirement error for NuGetPackager@0?

On , Azure Pipelines shows a retirement error for NuGetPackager@0, but the run does not fail. On , pipelines that still use NuGetPackager@0 fail.

Find it in your pipelines

With trasloco:

trasloco modernize --check

Install trasloco from the latest release.

With plain grep, nothing to install:

grep -rniwF 'NuGetPackager@0' --include='*.yml' --include='*.yaml' .

How to migrate

Migrate this step manually to NuGetCommand@2 with the pack command.

The task definition of the replacement is linked under official sources above.

NuGetPackager@0 retirement FAQ

Is NuGetPackager@0 deprecated?

Yes. NuGetPackager@0 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.

When does NuGetPackager@0 stop working?

NuGetPackager@0 is removed on 2027-03-15. Pipelines that still use it fail after removal.

What should I use instead of NuGetPackager@0?

Replace NuGetPackager@0 with NuGetCommand@2.