1

I have a release task (internal) that is currently in v4. I'd like start encouraging my users to move to the latest version. I followed these instructions to bundle multiple versions of the task, then I was hoping I could use the deprecated tag, but no such luck. It looks like that only works when the highest version of the task is marked deprecated and it has other implications such making the entire task harder to find.

How are tasks such as the Pester Test Runner only making later versions of the task (currently v6-v8 in this case) available? I tried publishing a version of my extension with the v1 visibility empty, and then with the entire task folder deleted, but v1 of the task was still available in the Azure DevOps ui in both cases.

JDH
  • 2,618
  • 5
  • 38
  • 48

1 Answers1

0

I am afraid you can’t do that. For the task just has v6-v8, the author just published v6-v8 version, so there isn’t v1, v2 etc… version.

You can make current task extension as deprecated and publish a new task extension (different id).

starian chen-MSFT
  • 33,174
  • 2
  • 29
  • 53