Skills Manager v1.23.2
发布日期:2026-06-17
递交范围:v1.23.1...v1.23.2
发布概览
- 同步状态准确性修复:copy 模式下包含 Python 脚本的 skill,在脚本运行后不再被误标为「中心有变更」——编译产物现在不再计入 skill 内容哈希。
用户可见更新
- 运行 skill 的 Python 脚本不再导致它被标记为未同步 —— 对于以 copy 模式部署的 skill,执行其 Python 脚本会在 agent 副本里生成
__pycache__/*.pyc字节码缓存。这些缓存文件此前被算进 skill 的内容哈希,导致副本与中心库不一致,该 skill 会一直被误标为「中心有变更」,直到手动重新同步。现在__pycache__目录与*.pyc文件已从内容哈希(以及来源差异视图)中排除,脚本运行后 skill 仍保持「与中心一致」。symlink 模式的 skill 从不受此影响,因为部署的链接与中心库是同一份文件。
开发者与治理更新
content_hash现在通过共享的list_content_files枚举忽略__pycache__与*.pyc,使更新标记与来源差异视图保持一致;新增覆盖__pycache__目录与散落.pyc文件的单元测试。
当前校验状态
- ✅ 跨平台构建通过(macOS Intel / macOS ARM / Windows x64 / Linux x64)
- ✅ TypeScript typecheck 通过
English release notes
Release date: 2026-06-17
Commit range: v1.23.1...v1.23.2
Release Overview
- A sync-accuracy fix: copy-mode skills that contain Python scripts no longer get falsely flagged "center changed" after their scripts run, because compiled-Python artifacts are now excluded from skill content hashing.
User-facing
- Running a skill's Python scripts no longer marks it as out-of-sync — For skills deployed in copy mode, executing their Python scripts created
__pycache__/*.pycbytecode caches inside the agent's copy. Those cache files were folded into the skill's content hash, so the copy diverged from the central library and the skill stayed flagged "center changed" until a manual re-sync.__pycache__directories and*.pycfiles are now excluded from content hashing (and from the source-diff view), so a skill keeps reading as in-sync after its scripts run. Symlink-mode skills were never affected, since the deployed link and the library are the same files.
Developer & Governance
content_hashnow ignores__pycache__and*.pycthrough the sharedlist_content_filesenumeration, so the update badge and the source-diff stay consistent; added unit tests covering both a__pycache__directory and a loose.pycfile.
Current Verification
- ✅ Cross-platform build passed (macOS Intel / macOS ARM / Windows x64 / Linux x64)
- ✅ TypeScript typecheck passed
完整变更:v1.23.1...v1.23.2