trasloco

GitHubRelease@0 is retired: replace it with GitHubRelease@1

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
GitHubRelease@1
Kind of migration
replacement with input changes
Automatic rewrite
Not yet. Automatic rewrite is planned for this kind of task (replacement with input changes). Today, trasloco modernize --check finds the step and you change it by hand.
Recommended action
Replace GitHubRelease@0 with GitHubRelease@1 and review the replacement inputs before updating the pipeline.

Official sources

Last verified:

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

On , Azure Pipelines shows a retirement error for GitHubRelease@0, but the run does not fail. On , pipelines that still use GitHubRelease@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 'GitHubRelease@0' --include='*.yml' --include='*.yaml' .

How to migrate

Replace GitHubRelease@0 with GitHubRelease@1 and review the replacement inputs before updating the pipeline.

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

GitHubRelease@0 retirement FAQ

Is GitHubRelease@0 deprecated?

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

When does GitHubRelease@0 stop working?

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

What should I use instead of GitHubRelease@0?

Replace GitHubRelease@0 with GitHubRelease@1.