Repository navigation
list-overrides: surface source: config in details output #1402
Description
Part of #1294 (Phase 8 of epic #1254). Branch: new-resolver-config.
What needs to Happen
Update src/fromager/commands/list_overrides.py. Note that inclusion is already done: a source: block sets has_config = True, which settings.list_overrides() already picks up. The gap is the details view:
- Add a
sourcecolumn/field (provider name, blank for legacy) to the table / CSV / JSON exporters. min_release_ageis currently read only fromps.resolver_dist.min_release_age; for a source-config package read it frompbi.source_resolver.min_release_agewhen present.
Tests
list-overrides --detailsincludes the source field for asource:-config package (e.g.provider: github-tag-git)- Legacy rows unchanged
Notes
Independent of the other #1294 sub-issues; can be worked on in any order.
Metadata
Metadata
Assignees
Labels
No labels
Activity
LalatenduMohanty commentedon Oct 30, 2026
Expanding this issue to also cover
package list-versions(was #1411, closed in favor of this one). Both commands ignoresource:settings:list-overrides: nosourcecolumn, andmin_release_ageis read only fromresolver_dist.list-versions: it calls theget_resolver_providerhook directly instead ofsources.get_source_provider(), so it lists versions from the wrong provider. Its cooldown status also readsmin_release_ageonly fromresolver_dist.Both can use one helper for the
min_release_agevalue. Extra tests forlist-versions:source:package lists versions from its configured provider.min_release_age, including0and--ignore-per-package-overrides.LalatenduMohanty commentedon Oct 30, 2026
Done in #1413, merged into
new-resolver-config.