Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Comments

@Alirazi1976123
Copy link

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.

Originally posted by @svenjr in dependabot/fetch-metadata#339 (comment)

@Fangliding Fangliding closed this as not planned Won't fix, can't repro, duplicate, stale Apr 17, 2024
@XTLS XTLS deleted a comment Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@Fangliding @Alirazi1976123 and others