Skip to content

fix(maintenance): explain managed component updates in upgrade dialog - #132

Merged
jaromil merged 1 commit into
mainfrom
feat/upgrade-components
Oct 25, 2026
Merged

jaromil merged 1 commit into
mainfrom
feat/upgrade-components

Conversation

@jaromil

@jaromil jaromil commented Oct 25, 2026

Copy link
Copy Markdown
Member

The Upgrade confirmation now names Gestalt, Agents, Mobile, context-mode and installed Serena/XERJ as the update scope, matching the shared manager behavior in dyne/gestalt#108. The GUI continues to delegate through the existing update-restart call, whose default updates all installed managed components after that manager change is installed.

Validation: format/license checks, TypeScript/Svelte checks (zero errors/warnings), lint, build and unit suite (2,599 passed, 2 skipped) passed. All three focused upgrade browser scenarios passed, including confirmation/restart at phone and desktop sizes and toast/retry behavior on failure; screenshots inspected. Full browser suite: 273 passed, one existing failure in model-policy-relay.spec.ts:287, previously reproduced on unchanged main. Svelte autofixer reported no issues.

@jaromil
jaromil merged commit 96310fd into main Oct 25, 2026
8 checks passed
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