Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Docker

What you expected to see, versus what you actually saw

Hey,

we have a Dockerfile, which has FROM private_registry/application/imagename:999 which was handled by dependabot perfectly up to 999 - Bump application/imagename from 994 to 995 -> Bump application/imagename from 995 to 997 -> Bump application/imagename from 997 to 999 . But now there are newer versions/tags - up to 1007. But dependabot keeps saying Latest version is 999.

Looking at the logs, dependabot even finds it (version/tag 1007) - by queriying https://private_registry/v2/application/imagename/tags/list and later https://private_registry:443/v2/application/imagename/manifests/1007. Yet the Latest version is 999

Manually changing the Dockerfile to FROM private_registry/application/imagename:1000 and running dependabot manually creates - as expected - the PR with the update to 1007.

update:

1007 is year_month and 999 is build_num hence they can not be compared.

Would it be possible, to define the format to be "tag_format_is_build_num" in the dependabot config? Else I would not know, how to resolve such cases, without breaking one or the other . Or is #11207 the way to go?

BR and thank you in advance
Christian