fix(dashboard): fall back to latest release viewer on version-pinned 404 - #633
Open
fengleli wants to merge 1 commit into
Open
fix(dashboard): fall back to latest release viewer on version-pinned 404#633fengleli wants to merge 1 commit into
fengleli wants to merge 1 commit into
Conversation
…d asset 404s The fast path pinned the prebuilt viewer to the plugin's package.json version, but that version can be ahead of the latest published viewer (e.g. 2.9.4 with no release while the viewer ships under 2.9.0). When the pinned asset is missing the launch failed and fell through to the heavy local build. Resolve the latest published release via 'gh release list' (or the GitHub API as a fallback) and retry the viewer there. Also surface the tokenized Dashboard URL as DASHBOARD_URL and log to /tmp/ua-dashboard.log.
Lum1104
self-requested a review
August 11, 2026 15:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The dashboard fast path pins the prebuilt viewer to the plugin's
package.jsonversion. That version can be ahead of the latest published viewer (e.g.2.9.4has no release asset while the viewer ships under2.9.0). When the pinned asset 404s, the launch fails and falls through to the heavy local build (which needspnpm install+ core build + Node >= 22), so the dashboard effectively never starts.Fix
Dashboard URL), automatically resolve the latest published release viagh release list(or the GitHub API as a fallback) and retry the viewer there.DASHBOARD_URL=line and log everything to/tmp/ua-dashboard.logso the agent can report it without scraping the terminal.Verification
Ran the updated fast path locally: pinned
2.9.4failed → resolvedv2.9.0→ launched the viewer and printed the tokenizedDASHBOARD_URL. Dashboard started successfully.This is a behavioral fix only in
understand-dashboard/SKILL.md; no code changes.