We're not updating all Markdown files which reference renovate/renovate docker tags

[HonkingGoose]

The latest "update references to renovate/renovate" PR ¹ did not update the references to renovate/renovate docker tags in the docs/usage/examples/self-hosting.md ² file.

Example of a reference that was missed: ²:

Docker

Renovate is available for Docker via an automated build renovate/renovate.
It builds latest based on the main branch and all semver tags are published too.
For example, all the following are valid tags:

docker run --rm renovate/renovate
docker run --rm renovate/renovate:25.69.4
docker run --rm renovate/renovate:25.69
docker run --rm renovate/renovate:25

Here is the Renovate configuration that applies to the created PR:

.github/default.json

Lines 46 to 58 in 1cfabab

	{
	"description": "Update references to Docker tags for renovate/renovate in Markdown files weekly",
	"matchPackageNames": ["renovate/renovate"],
	"matchPaths": [".md"],
	"extends": ["schedule:weekly"],
	"automerge": true,
	"stabilityDays": 0,
	"separateMajorMinor": false,
	"commitMessageTopic": "references to {{{depName}}}",
	"semanticCommitType": "docs",
	"semanticCommitScope": null,
	"additionalBranchPrefix": "docs-"
	},

I'm not sure what we need to change to get this working?

Footnotes

1. https://github.com/renovatebot/renovate/pull/12911 ↩

2. https://github.com/renovatebot/renovate/blob/main/docs/usage/examples/self-hosting.md ↩ ↩²

[viceice]

It's this regex manager:
https://github.com/renovatebot/.github/blob/main/default.json#L100-L108

I think we have a bug, when multiple different versions are updated.

[viceice]

/cc @rarkins

[rarkins]

Not sure we ever use the sha in docs? We could maybe simplify the regex

[viceice]

I don't think it's the regex. I think renovate fails to update with auto replace

[astellingwerf]

I didn't reconstruct a full timeline for the introduction of this issue, but I think I figured this out.

We're hoping to see a change on the file with the path docs/usage/examples/self-hosting.md. But that path means that it is subject to exclusion from renovation due to :ignoremodulesandtests. That preset is part of the config:base preset, which in turn is referenced on

.github/default.json

Line 5 in b0c3aa8

"config:base",

[astellingwerf]

That sorta means that this issue is dependent on renovatebot/renovate#11159, because the preset is set on the global level, meaning that today there is no way for ignorePresets to undo that.

[viceice]

That sorta means that this issue is dependent on renovatebot/renovate#11159, because the preset is set on the global level, meaning that today there is no way for ignorePresets to undo that.

i don't think that issue blocks this. we don't use any global config option in our presets.

[astellingwerf]

i don't think that issue blocks this. we don't use any global config option in our presets.

I think you're right @viceice, there was some confusion on my end on how ignorePreset doesn't work under certain conditions. It seems that they can't be applied on the package rule level. So I guess that if you want to exclude it on one package rule, you'll need to ignore the preset on the repo level, and then extend it on all except one package rule?