Refactor Bazel to use autoReplace + artifacts

[rarkins]

I think we should refactor our Bazel handling to use getArtifacts instead of trying to update them all in one go using updateDependency().

Whenever URLs, digests or checksums are dependent on the version - and not independently updatable - it should usually mean we use artifacts.

[rverma-dev]

@zharinov Also it seems that the current implementation for bezel rules doesn't handle tags. e.g. If I define the URL as "https://github.com/bazelbuild/rules_proto/archive/refs/tags/4.0.0-3.20.0.tar.gz", this is not detected at all

[viceice]

@zharinov Also it seems that the current implementation for bezel rules doesn't handle tags. e.g. If I define the URL as "https://github.com/bazelbuild/rules_proto/archive/refs/tags/4.0.0-3.20.0.tar.gz", this is not detected at all

that's not a tag, it's a archive of a tag. this is something totally different at renovate.

[cpsauer]

@viceice and @rverma-nsl: I think the above tag discussion might be arising because GitHub has changed the default URL for releases and tags on the release page. I've written up #17498 with more details, to keep that issue separate.

[rarkins]

Example from one of our fixtures: https://github.com/renovatebot/renovate/blob/e344b538f1b85c6a4fb0fb4f852a6fabb07392e1/lib/modules/manager/bazel/__fixtures__/WORKSPACE1#LL62

The url is https://github.com/bazelbuild/rules_nodejs/releases/download/5.5.3/rules_nodejs-core-5.5.3.tar.gz

Instead of detecting and updating 5.5.3 twice, we should only extract and update the first instance of it. The filename rules_nodejs-core-5.5.3.tar.gz would be the part updated as "artifacts".

[renovate-release]

🎉 This issue has been resolved in version 34.132.0 🎉

The release is available on:

• GitHub release
• 34.132.0

Your semantic-release bot 📦🚀