build: build renovate docker images on release

[viceice]

Changes

Build our renovate images after the npm release

Context

requires those to be merged before:

• ci: stop publish docker-renovate#2118
• ci: stop publishing docker-renovate-full#2650

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 select 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

[secustor]

LGTM so far

[rarkins]

Do you anticipate having any "race conditions" where you publish version x.y.z to npmjs and then the corresponding Docker image fails to install the same version because the npmjs CDN says it's not available?

Is it already the case that every version we publish to npm will have a corresponding version on Docker? i.e. GitHub doesn't cancel duplicate workflows, and if a Docker publish fails after npm publish succeeds, is there a way to recover?

Do we have a nice way to roll forward and back with this approach after merge if we find problems?

[viceice]

Do you anticipate having any "race conditions" where you publish version x.y.z to npmjs and then the corresponding Docker image fails to install the same version because the npmjs CDN says it's not available?

🤔 Didn't thought about that yet.

Is it already the case that every version we publish to npm will have a corresponding version on Docker? i.e. GitHub doesn't cancel duplicate workflows, and if a Docker publish fails after npm publish succeeds, is there a way to recover?

We don't publish all versions to docker yet, because the current images are not updated that often and we only rebuild last version.

Do we have a nice way to roll forward and back with this approach after merge if we find problems?

Currently the docker images are not published. I've disabled to just test the docker build on release.
If build succeeds fine, the we can enable image publishing in a new PR. If build fails because of npmjs issues, then we can revert / or fix the build first by another approach. (not using npmjs renovate, but using a local build)

[renovate-release]

🎉 This PR is included in version 37.139.0 🎉

The release is available on:

• GitHub release
• 37.139.0

Your semantic-release bot 📦🚀