chore: reconfigure renovate

[viceice]

Add some regex managers to update the Dockerfile

[rarkins]

I would like to consider having a single manager and using comments above the env instead, what do you think?

Alternatively, I think these env vars are so common in Dockerfiles that we could make them presets and maybe even part of config:base

[viceice]

Yeah, working on it, will try it on docker composer image repo first

[viceice]

@rarkins Ready to review again.

[viceice]

same regex works for renovatebot/composer 💪

[rarkins]

Code suggestions is broken for me, so doing it as a comment here

Instead of # renovate: github-releases/docker/docker-ce&versioning=docker, do you think # renovate: github-releases/docker/docker-ce versioning=docker is cleaner? i.e. a space divider instead of &

[viceice]

Code suggestions is broken for me, so doing it as a comment here

Instead of # renovate: github-releases/docker/docker-ce&versioning=docker, do you think # renovate: github-releases/docker/docker-ce versioning=docker is cleaner? i.e. a space divider instead of &

What about:

# renovate: datasource=github-releases name=docker/docker-ce versioning=docker
ENV DOCKER_VERSION=19.03.5

or

# renovate: datasource:github-releases name:docker/docker-ce versioning:docker
ENV DOCKER_VERSION=19.03.5

[rarkins]

I like this approach best: # renovate: datasource=github-releases name=docker/docker-ce versioning=docker

My only doubt is whether to use depName and optionally lookupName for consistency

[viceice]

🤔 Ok, we can use wharever we want as key, because it's only relevant for regex matching, but the key will not be the capture group name by default. We would make it explicit. I'll try to update the regex.

[rarkins]

I think the simplest approach is to use the capture groups, and also plenty will probably copy from this repo's config to learn, so it can be good for consistency to have like depName=(<?depName>.*?)

[viceice]

see current changes

[viceice]

Working, see #5728 💪