feat: add azure pipelines built-in tasks version data

[JamieMagee]

Changes

Adds version information for Azure Pipelines built-in tasks.

There is no public API that exposes this information. I checked with the team that maintains these tasks, and parsing the git history was the recommended way to extract version information. I don't believe doing this during a Renovate run is feasible, hence adding it as static information in the repository.

The script currently catches 3 2 exceptions throughout the azure-pipelines-tasks repository's history:

• Failed to parse Tasks/CondaEnvironmentV0/task.json at 7ff8f87757903515cdcf521a76f92626bd06ab2a
  • CondaEnvironmentV0/task.json was moved to CondaEnvironmentV1/task.json
• Failed to parse Tasks/DownloadPipelineArtifactV2/task.json at d0c0a1cce48931d8ba009ef3db51651c47b0c924
  • Someone added a comment to DownloadPipelineArtifactV2/task.json
• Failed to parse Tasks/IISWebAppDeployment/task.json at 05114960d2286a029cf1cbd99380df3a8332e9be
  • The file was deleted (and later re-added)

If there are any git wizards who know how to exclude renames and deletions from git rev-list please let me know.

Context

• Part of Support for Azure Pipelines Tasks #15818
• Required by feat(datasource/azure-pipelines-tasks): add azure-pipelines-tasks datasource #16904

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

I think this algorithm you created needs some documentation to explain the "why", in case someone else needs to maintain it :)

[viceice]

otherwise LGTM

[rarkins]

Considering that it seems quite slow, how/when will this command need to be called?

[JamieMagee]

I think once a week should cover it. Shall I create a follow-up task to write a weekly scheduled GitHub Actions workflow?

[rarkins]

Yeah, that would be good. I just wanted to make sure it doesn't run as part of yarn test or any time like that. If it's only manually invoked then that's fine by me

[JamieMagee]

This PR adds the script, but doesn't run it anywhere. It requires a manual run, same as the update:distro-info script we have to update Debian and Ubuntu version information.

[viceice]

I think once a week should cover it. Shall I create a follow-up task to write a weekly scheduled GitHub Actions workflow?

sounds good, like that. how should it notify us of changes? ideally with an update PR. 🤗

[JamieMagee]

sounds good, like that. how should it notify us of changes? ideally with an update PR. 🤗

I created #17050

[renovate-release]

🎉 This PR is included in version 32.153.0 🎉

The release is available on:

• GitHub release
• 32.153.0

Your semantic-release bot 📦🚀