Relationships
#3342 Rescore scores the newest version, but the scorecard reads the stable one
Opened by skunk-ape · 10/13/2026
POST /api/v1/extensions//score (the Rescore button) enqueues getLatestNonYankedVersion(), the newest version on any channel. The scorecard, the extension page and the listing's license flag all read resolveScorecardVersion(): latest stable, falling back to rc and then beta.
When an extension's newest version is an rc or beta ahead of its stable, Rescore analyses the prerelease. The scorecard keeps reading the stable version, which may never have been scored, and keeps reporting not_scored. With unlicensed extensions now hidden from browsing (an unknown license counts as hidden), such an extension can't be brought back by pressing Rescore.
Reproduced locally on the seeded @swampadmin/container-runtime (stable 2026.02.15.0, newer 2026.03.15.0): Rescore wrote extension_version_meta for 2026.03.15.0, and the score API still returns available:false, reason:not_scored.
Fix: have handlePostScore score resolveScorecardVersion(ext), or both versions when they differ.
Found while working on Lab 3323; none of the 31 currently unscored public extensions on prod is affected.
Open
No activity in this phase yet.
system commented 10/13/2026, 2:29:11 AM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.