Repository navigation
[desktop] In-app update does not bump official profile packages; next launch fails with "required plugin did not activate" #13748
yiheng-zyh
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment
zh-CN@deepseek-ai/dsh-desktop0.2.2-rc.5 (Electron 44.7.0, Node 24.21.0)~/.dsh/profiles/desktop, migrated from 0.1.x and customized with third-party pluginswebprofile)Summary
The Windows in-app updater installed 0.2.2-rc.5 while the 0.2.2-rc.3 process was still running. The app image (
DeepSeek Harness.exe,resources/app.asar) was replaced, but the official@deepseek-ai/*packages in the desktop profile stayed pinned at 0.2.2-rc.3.On the next launch, the profile startup audit disabled
@deepseek-ai/dsh-authorization@0.2.2-rc.3as incompatible with the rc.5 runtime. This cascaded:deepseek-accountwaited forauthorizationllmconsumer waited forllmagent-loop(a required plugin) waited forllmand the host exited with a fatal startup error. The app cannot reach its own in-app plugin manager because the host never boots.
Timeline (local time, UTC+8)
Actual behavior
The essential host startup audit is quoted above. A trimmed and redacted host crash log is available on request; the quoted audit is sufficient to reproduce the dependency chain.
Why the built-in recovery button does not help
The fatal dialog offers “Disable third-party plugins, back up profile patch, and restart”. That cannot fix this failure, because the disabled/failing packages are official
@deepseek-ai/*profile dependencies, not third-party bundles.Why this is an updater/profile ownership problem
The desktop profile is declared app-exclusive:
Yet the app updater does not bump the official
@deepseek-ai/*packages it ships for that profile. Those dependencies are exact-pinned, and the compatibility check is exact-version (authorization@0.2.2-rc.3vsdsh 0.2.2-rc.5), so a one-version skew disables the package instead of warning or continuing.Before recovery, the profile manifest contained (abbreviated):
{ "dependencies": { "@deepseek-ai/dsh-authorization": "0.2.2-rc.3", "@deepseek-ai/dsh-credentials": "0.2.2-rc.3", "@deepseek-ai/dsh-llm": "0.2.2-rc.3", "@deepseek-ai/dsh-llm-pi-ai": "0.2.2-rc.3", "@deepseek-ai/dsh-subagent-codex": "0.2.2-rc.3" } }Expected behavior
@deepseek-ai/*packages in the app-managed desktop profile as part of the app update: bump them to the new app version atomically (with a manifest/lockfile backup), or refuse to install the update with a clear “profile is out of sync” message.dsh plugin --profile desktop add <official packages>@<installed version>Workaround
Updating the 10 official direct dependencies to the installed app version restores startup:
After the sync, the app boots and
account/getStatereturnsok.Note
A separate compatibility break also affected a third-party plugin (
dsh-sentinel@0.11.1calledctx.agents.roots(), removed in 0.2.2-rc.2). That is expected under the 0.2.2 plugin migration and was fixed by upgrading the plugin to 0.15.0. It is not the cause of this startup failure; the startup failure is entirely the official profile package mismatch.Related discussions
session-query-sqlite); the app still boots and the UI is reachable.@deepseek-ai/*dependencies with the incoming runtime; this report is the Windows data point where the mismatch is fatal instead of partial.@deepseek-ai/dsh-*packages (CLI path, same preflight mechanism).What is new here: on Windows the stale package is a core dependency (
dsh-authorization), so the cascade reachesagent-loop, which isrequired. The host therefore never starts at all 鈥?no UI and no plugin manager 鈥?and the built-in "disable third-party plugins" recovery cannot help because the failing packages are official.All reactions