The Dependencies tab sorts PR-type badges (lock-file-maintenance, minor, major, etc.) within each repo group, but doesn't follow Renovate's own documented risk order — digest-type updates are currently indistinguishable from patch updates, and the sort order doesn't fully reflect Renovate's stated risk ranking (lockFileMaintenance safest, then digest, patch, minor, major).
Separately, several dependency PRs show no type badge at all even though they're valid Renovate updates (e.g. a single-target-version title like "update dependency X to vY" with no diff shown). Investigation traced this to two compounding issues: the title-parsing logic doesn't recognize a few common Renovate title phrasings (so it can't extract even a package name for some ecosystems), and the async fallback that fetches PR bodies to fill in missing classification can get permanently stuck for the rest of a session if a single request hangs, silently blocking all further classification until a page reload.
Expected: badges should sort by actual risk (safest first), every valid dependency PR should get a badge when classifiable, and a stuck classification fetch should recover on its own instead of requiring a manual reload.
The Dependencies tab sorts PR-type badges (lock-file-maintenance, minor, major, etc.) within each repo group, but doesn't follow Renovate's own documented risk order — digest-type updates are currently indistinguishable from patch updates, and the sort order doesn't fully reflect Renovate's stated risk ranking (lockFileMaintenance safest, then digest, patch, minor, major).
Separately, several dependency PRs show no type badge at all even though they're valid Renovate updates (e.g. a single-target-version title like "update dependency X to vY" with no diff shown). Investigation traced this to two compounding issues: the title-parsing logic doesn't recognize a few common Renovate title phrasings (so it can't extract even a package name for some ecosystems), and the async fallback that fetches PR bodies to fill in missing classification can get permanently stuck for the rest of a session if a single request hangs, silently blocking all further classification until a page reload.
Expected: badges should sort by actual risk (safest first), every valid dependency PR should get a badge when classifiable, and a stuck classification fetch should recover on its own instead of requiring a manual reload.