Skip to content

v0.1.2 — bulk selection, updater fix, discovered plugin caches / 批量选择、更新器修复、插件缓存自动发现

Latest

Choose a tag to compare

@you112358 you112358 released this 20 Nov 09:22

v0.1.2 — bulk selection, real updater cleanup, discovered plugin caches / 批量选择、更新器缓存修复、插件缓存自动发现

Features

  • Select all / deselect all in the cleaning list, with a live {n}/{m} selected counter. Select-all only includes rows that actually hold data, so an empty page cannot select nothing by accident.
    • 清理列表新增「全选 / 全不选」,并实时显示「已选 n/m 项」。全选只会选中真正有数据的行。
  • Plugin caches are one generic target now. They are discovered from the active profile: a plugin can declare dsh.cache in its package.json (string, array, or { path, mode }), and conventional cache directories (cache, .cache, compile-cache, logs, tmp) next to a plugin's data roots are picked up automatically. New options pluginCacheDiscovery (default true) and pluginCacheExtraPaths. No per-plugin adapter table.
    • 插件缓存改为通用项:从当前Profile自动发现,支持插件在自己的 package.json 里声明 dsh.cache,也会识别数据目录旁的常规缓存目录。不再内置任何插件适配表。
  • New terminal helper node scripts/clean-cli.mjs cleans the same targets from a terminal — the escape hatch for caches the running desktop client keeps open.

Fixes

  • The updater download cache can be cleaned. Its unit pointed at its own allow-listed root, so the safety fence refused every deletion while the row still looked cleanable. Roots listed in CLEANABLE_ROOTS may now be emptied in contents mode, and locked files get four attempts (80 ms, then 200 ms) before being reported.
    • 更新器下载缓存现在可以正常清理:此前它指向自己的允许根目录,安全围栏拒绝删除所有内容。
  • Caches held open by the running client are reported as in use, not as errors. Chromium keeps the network cache journal open while the desktop client runs, so a row can honestly only be cleaned after the client quits. Those entries now show a dedicated note, are excluded from the error count, and the tool prints a separate "held open by the running client" section.
    • 被运行中客户端占用的缓存不再计为错误:行内显示「被客户端占用」,清理报告不再统计它们。
  • The clean report banner no longer repeats a "skipped" count for rows that already explain themselves.
  • row.restart was always undefined in clean results; it is now carried through so the "restart to reclaim" hint works.

Removed

  • The dsh-session-projections target (cleaning it caused display problems). The id now returns UNKNOWN_TARGET; 11 targets remain.

Docs

  • Both READMEs updated: 11-target table, dsh.cache plugin cache discovery, the in-use caveat with the CLI, new configuration keys.
  • CI now also runs the safety fence, plugin-cache discovery and real-cleanup checks.

Upgrade

# in DeepSeek Harness
plugin_manager action=remove_bundle   target=dsh-cache-cleaner
plugin_manager action=install_bundle  target=/path/to/dsh-cache-cleaner

or toggle the plugin row off/on in Settings → Plugins, then refresh the page (the client bundle is served with a new revision).