Skip to content

fix: hotfix v0.9.4 — tolerate name/id mismatch when resolving selected harness#253

Merged
eyelock merged 1 commit into
mainfrom
hotfix/v0.9.4
May 2, 2026
Merged

fix: hotfix v0.9.4 — tolerate name/id mismatch when resolving selected harness#253
eyelock merged 1 commit into
mainfrom
hotfix/v0.9.4

Conversation

@eyelock
Copy link
Copy Markdown
Owner

@eyelock eyelock commented May 2, 2026

Summary

Hotfix release v0.9.4. Cherry-picks fix onto v0.9.3.

Fix: HarnessRepository.selectedHarness matched only on id, but YNHPersistence keys associations by bare name. For any namespaced harness install the lookup missed and the launch sheet rendered as a blank rounded rectangle.

Change: Match by id first, fall back to name. Apply the same fallback in the stale-selection eviction inside refresh().

Affects v0.9.3. Closes #252.

Checklist

  • Fix is scoped to the targeted regression — no unrelated changes
  • CHANGELOG updated on hotfix branch
  • CI must pass before merge

🤖 Generated with Claude Code

…ss (#252)

`Harness.id` is `"namespace/name"` for namespaced installs but
`YNHPersistence` keys associations by bare `name`. The Launch <harness>
flow on worktree rows passes the persisted name through and sets
`selectedHarnessName = name`, but `HarnessRepository.selectedHarness`
matched on `id` only — for any namespaced install the lookup missed,
the launch sheet's content closure returned nothing, and the sheet
rendered as a blank rounded rectangle that never populated and could
only be dismissed with Esc.

Make `selectedHarness` match by `id` then fall back to `name`. Apply
the same rule to the stale-selection eviction inside `refresh()` so
the next list refresh doesn't immediately clear a name-keyed selection.

Affects v0.9.3 — also forward-ported via hotfix release.

Co-authored-by: David Collie <support@eyelock.net>
@eyelock eyelock merged commit 27a1e73 into main May 2, 2026
15 checks passed
@eyelock eyelock deleted the hotfix/v0.9.4 branch May 2, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant