Is there an existing issue for this?
Describe the bug
DashboardRunStore.LoadRuns excludes metadata whose schema version differs from the current version. PruneRuns only iterates the successfully loaded _runs snapshot.
After a Dashboard schema upgrade, older-schema run directories become invisible to both selection and retention, so storage can grow beyond the advertised run limit.
Expected Behavior
Incompatible historical runs should remain non-selectable but still participate in retention cleanup.
Steps To Reproduce
- Create
Run history with one Dashboard schema version.
- Start a Dashboard whose schema version has advanced.
- Create enough new runs to trigger retention.
- The old-schema directories are never selected as pruning candidates.
Exceptions (if any)
N/A
Aspire doctor output
Aspire CLI 13.6.0-pr.18924.g5ee63941
Windows 10.0.26200 and Ubuntu 24.04.3
Anything else?
Related to #18924. Source: src/Aspire.Dashboard/ServiceClient/DashboardRunStore.cs:336-369,440-465. This was mentioned during PR review and remains on current main.
Is there an existing issue for this?
Describe the bug
DashboardRunStore.LoadRunsexcludes metadata whose schema version differs from the current version.PruneRunsonly iterates the successfully loaded_runssnapshot.After a Dashboard schema upgrade, older-schema run directories become invisible to both selection and retention, so storage can grow beyond the advertised run limit.
Expected Behavior
Incompatible historical runs should remain non-selectable but still participate in retention cleanup.
Steps To Reproduce
Runhistory with one Dashboard schema version.Exceptions (if any)
N/A
Aspire doctor output
Anything else?
Related to #18924. Source:
src/Aspire.Dashboard/ServiceClient/DashboardRunStore.cs:336-369,440-465. This was mentioned during PR review and remains on currentmain.