You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing this as well for internal Docker image update tags (either incoming or outgoing) have a prefixing v then the outputs.update-type is null#2195
Closed
Alirazi1976123 opened this issue
Jun 11, 2023
· 1 comment
We are seeing this as well for internal Docker image update tags (either incoming or outgoing) have a prefixing v then the outputs.update-type is null
We have tried every variant of this and we have found (using internal docker builds) the following:
v1.5.1 to v1.5.2 -> outputs.update-type: null v1.5.1 to 1.5.2 -> outputs.update-type: null 1.5.2 to v1.5.3 -> outputs.update-type: null 1.5.2 to 1.5.3 -> outputs.update-type: patch
While it is true that this sort of tag is not strictly semver compliant, I would expect Dependabot to be able to infer this sort of thing with a non-complex tag.
I did just create an issue in Dependabot Core but I looked here to see this and thought it was out issue so I closed it.
We are seeing this as well for internal Docker image update tags (either incoming or outgoing) have a prefixing
v
then theoutputs.update-type
isnull
We have tried every variant of this and we have found (using internal docker builds) the following:
v1.5.1
tov1.5.2
->outputs.update-type: null
v1.5.1
to1.5.2
->outputs.update-type: null
1.5.2
tov1.5.3
->outputs.update-type: null
1.5.2
to1.5.3
->outputs.update-type: patch
While it is true that this sort of tag is not strictly semver compliant, I would expect Dependabot to be able to infer this sort of thing with a non-complex tag.
I did just create an issue in Dependabot Core but I looked here to see this and thought it was out issue so I closed it.
Originally posted by @svenjr in dependabot/fetch-metadata#339 (comment)
The text was updated successfully, but these errors were encountered: