Repository navigation
自 v0.5.3 以来的修复(对应 npm 0.5.4)
-
分块质量(#67 / #68):过滤已识别的纯标记片段;在同一标题节内合并较短的智能分块;保留字面代码和正文;已完成的空索引不会在每次启动时反复恢复。
Chunk quality (#67 / #68): filter recognized markup-only chunks, merge short semantic chunks within the same heading section, preserve literal code and body text; completed empty indexes no longer get repeatedly restored on every startup. -
启动与删除(#70 / #73 / #74):产物清理改为后台执行,最多四个 worker;删除前检查最新 revision;卸载时取消。删除知识库时同时清理文档记录;启动恢复会移除旧版本遗留的无主记录。
Startup & deletion (#70 / #73 / #74): artifact cleanup runs in the background with up to four workers; the latest revision is checked before deletion; canceled on uninstall. Deleting a base now also cleans document records; startup recovery removes orphan records left by older versions. -
桌面布局(#69 / #72 / #75):标题和关闭按钮避开原生窗口控件;共享页脚入口自动分配宽度;折叠侧边栏时图标纵向排列。
Desktop layout (#69 / #72 / #75): title and close button avoid native window controls; shared footer entries auto-distribute width; icons stack vertically when the sidebar is collapsed. -
宿主依赖(#71):明确声明运行时使用的
zodpeer dependency,并在发布包检查中验证。
Host dependency (#71): explicitly declare thezodpeer dependency used at runtime and verify it in the release package check.
升级说明
从 0.5.3 升级无需数据库格式迁移或重新下载模型。已有索引保持可用;需要应用新分块规则的文档可手动重建。大量历史无主记录的首次清理仍可能耗时。
Upgrade: No database format migration or model re-download is required when upgrading from 0.5.3. Existing indexes remain usable; documents that need the new chunking rules can be rebuilt manually. The first cleanup of a large number of legacy orphan records may still take some time.
相关 PR:
完整变更:
v0.5.3...v0.5.4