Provide more visibility into filtered versions #29152
rarkins
started this conversation in
Suggest an Idea
Replies: 1 comment
-
Makes sense. On DEBUG we should log how many releases have been discarded by reason e.g. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
There are now many reasons why a "newer" version might be ignored or suppressed, including:
allowedVersions
andminimumReleaseAge
configurationconstraintsFiltering=strict
compatibility
filteringI don't want to make the information "in your face" (demanding users look at it) but I do want to make it visible at least in logs for those who are interested or troubleshooting.
Generally speaking our approach to filtering is that the initial list we get from a datasource lookup gets progressively narrowed before eventually being grouped into "buckets" (e.g. major, non-major). If a version is filtered out for more than one reason (e.g it could be unstable and not satisfying minimumReleaseAge) then we don't check it for every reason once it's already failed one.
In some cases like npm packages or the Node.js version it would make a lot of sense to have full visibility into which reason any version was filtered out. For other cases like Docker tags - including Node.js docker tags - I'm not sure we want to list every single version from a wrong "compatibility" (e.g. -alpine -debian -slim, etc) as it can be too much information.
Beta Was this translation helpful? Give feedback.
All reactions