Thomas
Thomas
If it helps, I've copied the output from the linked debug log and put it in this [gist](https://gist.github.com/uhthomas/da50bee0a31a3e0755bc5e6644780f34).
> the logs doesn't contain the warning, so wrong run Yes they do. https://gist.github.com/uhthomas/da50bee0a31a3e0755bc5e6644780f34#file-renovate-debug-log-L254
@viceice I did see that issue, but it's not quite the same. The replacement rules work as expected in our case, but it just seems that for some reason Renovate...
Okay @viceice, I have a full working reproduction now. Repository: https://github.com/uhthomas/renovate20304/tree/445bbce6bf13dc2da5f4350e10c74d8f9d946601 Logs: https://app.renovatebot.com/dashboard#github/uhthomas/renovate20304/1001783011 ([gist](https://gist.github.com/uhthomas/3b905068579acefa299cc7e37e70f528)). Here's what Renovate is trying to do: See: https://github.com/uhthomas/renovate20304/pull/3/files It's trying to update the original image...
I think this is the same behaviour as self hosted. We saw correct replacement in some repos, but just a pin PR with the incorrect digest in others.
Is there anything I can do to help fix this?
I believe this issue occurs even if the original dependency was pinned. I can add that to the reproduction repository to prove it if that would be helpful.
I tried disabling digest pinning for those deps, but the same thing happened. Have I misconfigured it? ```json { "packageRules": { "matchDatasources": [ "docker" ], "matchPackageNames": [ "example.com/old" ], "pinDigests":...