Releases: semantic-craft/patchbay-releases
Releases · semantic-craft/patchbay-releases
Release list
Patchbay v1.30.0
Patchbay v1.30.0
发布日期:2026-07-18
发布概览
- 交付 Liquid Glass 工作台整轮(#26):工作台成为主屏并获得原生玻璃窗口质感,链路维护改为异常驱动、修复可撤销,并支持 Preset 驱动的项目接入。
用户可见更新
- Liquid Glass 工作台 — 项目工作台成为主路由,浅/深两套玻璃皮肤:壁纸底的窗口壳、玻璃侧栏与悬浮玻璃卡片。
- macOS 窗口级玻璃 — 窗口转为透明:macOS 26 上启用真 Liquid Glass(NSGlassEffectView),旧版 macOS 回退磨砂 vibrancy,两者都不可用时自动退回不透明底——功能不减。
- 原生外观跟随主题 — 在设置中选择浅色/深色/跟随系统时,原生窗口材质与标题栏同步切换,玻璃不再与界面主题错配。
- 异常驱动的链路维护 — 链路健康时呈现安静的全绿屏;断链浮现为证据卡(候选路径、git 线索),通过确定性的 plan/apply 修复动线处理,支持步进直播与暂停/接管。
- 修复留痕与撤销 — 每次修复落账 journal 并记录逆操作,可一键受保护地撤销。
- 共因批量重链 — 仓库迁移导致的大面积断链聚合为一张共因卡,一键批量重链。
- 反哺提示卡 — 原件仓库存在未提交改动时浮现琥珀色提示卡。
- Chain Preset 与接入向导 — 可把当前技能集合存为 Preset 并从 Preset 栏应用;零链接项目通过三步向导(选来源 → 挑技能 → 建入口)完成接入。
开发者与治理更新
- 窗口玻璃走三档运行时探测(
liquid-glass/vibrancy/none),降级判定为纯函数并有单测覆盖;仅在确认原生材质就位后 CSS 壁纸才让位。 - 采用
tauri-plugin-liquid-glass(自带 cocoa/objc 绑定)规避 window-vibrancy 0.6/0.8 符号冲突(tauri#15478);已接受偏差记录于 #37:非焦点窗口恒为雾面、macOSPrivateApi不符 App Store 合规。 - Agent instructions 支持矩阵调研(issue #3)落入
docs/research/。
当前校验状态
- ✅ macOS 构建通过(Intel / Apple Silicon)
- ✅ TypeScript typecheck 通过
English release notes
Release date: 2026-07-18
Release Overview
- Delivers the Liquid Glass workbench round (#26): the workbench becomes the home screen with a native glass window treatment, exception-driven chain maintenance with undoable repairs, and preset-driven onboarding.
User-facing
- Liquid Glass workbench — the project workbench is now the home route, dressed in a light/dark glass skin: a wallpaper-backed window shell, glass sidebar, and floating glass cards.
- Window-level glass on macOS — the window turns transparent with real Liquid Glass (NSGlassEffectView) on macOS 26, frosted vibrancy on older macOS, and an automatic opaque fallback when neither applies — features never degrade.
- Native appearance follows your theme — picking Light/Dark/System in Settings now also drives the native window material and title bar, so the glass never mismatches the UI theme.
- Exception-driven chain maintenance — a calm all-clear screen when links are healthy; broken links surface as evidence cards with candidate paths and git clues, fixed through a deterministic plan/apply repair flow with live step progress and pause/take-over.
- Repair journal with undo — every applied repair is journaled with its reverse operation for one-click, guarded undo.
- Common-cause batch relink — repository moves that break many links at once aggregate into a single cause card with one-click batch relinking.
- Feed-upstream hint — an amber card surfaces uncommitted changes sitting in original skill repositories.
- Chain presets and onboarding wizard — save the current skill set as a preset, apply it from the preset bar, and onboard zero-link projects through a three-step wizard (source → skills → entry files).
Developer & Governance
- Window glass ships behind a three-tier runtime probe (
liquid-glass/vibrancy/none) with a pure, unit-tested degradation decision; the CSS wallpaper stays opaque unless a native material is confirmed behind the webview. - Adopted
tauri-plugin-liquid-glass(bundled cocoa/objc bindings) to avoid the window-vibrancy 0.6/0.8 duplicate-symbol conflict (tauri#15478). Accepted deviations recorded on #37: unfocused windows always frost;macOSPrivateApiis App Store-incompatible. - The agent-instructions support-matrix research (issue #3) landed in
docs/research/.
Current Verification
- ✅ macOS build passed (Intel / Apple Silicon)
- ✅ TypeScript typecheck passed
Patchbay v1.29.4
Patchbay v1.29.4
发布日期:2026-07-16
发布概览
- 在整理后的 Patchbay 代码库上增加由用户确认的桌面应用自动更新,并完成剩余的仓库治理 tickets。
用户可见更新
- 自动检查签名更新 — 官方 macOS 版本会在启动后每天检查一次 Patchbay 公开发布通道,发现新版本时持续显示可操作提示。
- 安装仍由用户控制 — 只有在用户点击“安装并重启”后,Patchbay 才会下载、校验、安装并重启;自动检查可以关闭,手动检查与发布页下载兜底仍然保留。
- 按目标版本确认 — 如果提示出现后可用版本发生变化,Patchbay 会针对新的目标版本再次询问,不会沿用旧版本的确认直接安装。
- 导航与三层链路更清晰 — 侧边栏围绕技能库、安装、链路总览、项目链路、原件仓库、诊断和备份组织;重复的 Dashboard 与全局工作区入口已并入对应的主入口。
- 接入 Patchbay Central 与 Qoder Work — 中央库安装的技能可以进入项目级三层链路,并支持 Qoder Work 的项目技能入口,同时不会把 Qoder 厂商管理的全局目录误报为策略违规。
开发者与治理更新
- 新增经 TDD 覆盖的更新协调器,注入设置、时间、更新器与进程边界;补充启动通知渲染测试,以及英文、简体中文和繁体中文完整文案。
- 注册 Tauri process 插件且只开放重启权限;发布契约现覆盖 updater/process 的依赖、注册、权限、公开端点、签名公钥和启动接线。
- 完成剩余的 CLI 决策工作流与 canonical instructions wrapper 合同,并在发版前删除退役生成资产和无用代码。
- 合并重复的导航与备份界面,移除未使用的
@hello-pangea/dnd依赖,并按发布检查要求完成全仓 Rust 格式化。
当前校验状态
- ✅ macOS 构建通过(Intel / Apple Silicon)
- ✅ TypeScript typecheck 通过
English release notes
Release date: 2026-07-16
Release Overview
- Adds user-approved desktop auto-updates and completes the remaining repository-governance tickets on the cleaned Patchbay codebase.
User-facing
- Automatic signed update checks — official macOS builds check the public Patchbay release channel once per day after startup and show a persistent prompt when a new version is available.
- Installation remains under user control — Patchbay downloads, verifies, installs, and restarts only after the user chooses Install and restart; automatic checks can be disabled, and manual checking plus release-page downloads remain available.
- Version-specific approval — if the available release changes after a prompt appears, Patchbay asks again for the new target version instead of installing it under the earlier approval.
- Clearer navigation and three-tier flow — the sidebar now centers on the library, installation, link topology, project links, source repositories, diagnostics, and backup; redundant dashboard and global-workspace routes were folded into their canonical destinations.
- Patchbay Central and Qoder Work integration — centrally installed skills can enter the project-only three-tier chain, including Qoder Work's project skill surface, without treating Qoder's vendor-managed global directory as a policy violation.
Developer & Governance
- Added a TDD-covered updater coordinator with injected settings, time, updater, and process boundaries, plus rendered startup-notification tests and complete English, Simplified Chinese, and Traditional Chinese copy.
- Registered the Tauri process plugin with restart-only permission and expanded the release contract across updater/process dependencies, registrations, permissions, public endpoint, signing key, and startup wiring.
- Completed the outstanding CLI decision workflow and canonical instructions wrapper contracts, then removed retired generated assets and dead code before release.
- Consolidated duplicate navigation and backup surfaces, removed the unused
@hello-pangea/dnddependency, and applied repository-wide Rust formatting enforced by the release checks.
Current Verification
- ✅ macOS build passed (Intel / Apple Silicon)
- ✅ TypeScript typecheck passed
Patchbay v1.29.3
Patchbay v1.29.3
发布日期:2026-07-14
发布概览
- 从独立私有源码仓完整验证 Patchbay 的双仓发布架构。
用户可见更新
- 私有开发、公开更新保持稳定 — 签名后的 macOS 更新继续通过
semantic-craft/patchbay-releases提供,不依赖公开源码访问。
开发者与治理更新
- 本版本完全由私有独立源码仓完成准备、打 tag、构建、签名、公证与发布派发。
- 发布专用 GitHub App 继续只为公开 release 仓签发短期、单仓库范围的令牌。
当前校验状态
- ✅ macOS 构建通过(Intel / Apple Silicon)
- ✅ TypeScript typecheck 通过
English release notes
Release date: 2026-07-14
Release Overview
- Verifies Patchbay's complete two-repository release architecture from an independent private source repository.
User-facing
- Stable public updates from private development — signed macOS updates continue through
semantic-craft/patchbay-releaseswith no dependency on public source access.
Developer & Governance
- This release is prepared, tagged, built, signed, notarized, and dispatched entirely from the private standalone source repository.
- The release-only GitHub App continues to mint short-lived tokens scoped exclusively to the public release repository.
Current Verification
- ✅ macOS build passed (Intel / Apple Silicon)
- ✅ TypeScript typecheck passed
Patchbay v1.29.2
Patchbay v1.29.2
发布日期:2026-07-14
发布概览
- 将 Patchbay 私有源码仓库与公开发布通道彻底分离。
用户可见更新
- 独立公开更新通道 — 应用内更新检查、版本链接和下载现在统一使用
semantic-craft/patchbay-releases;源码仓库保持私有的同时,签名后的 macOS 更新仍可公开获取。
开发者与治理更新
- 发布自动化改用独立的 Patchbay Release Publisher GitHub App 签发短期令牌;该 App 只安装在公开发布仓库,并且仅有 Contents 写权限。
- 私有源码工作流可以跨仓构建、签名、公证、验证并发布产物,不公开源码历史,也不使用可长期复用的个人令牌。
当前校验状态
- ✅ macOS 构建通过(Intel / Apple Silicon)
- ✅ TypeScript typecheck 通过
English release notes
Release date: 2026-07-14
Release Overview
- Separates Patchbay's private source repository from its public release channel.
User-facing
- Dedicated public update channel — in-app update checks, release links, and downloads now use
semantic-craft/patchbay-releases, so signed macOS updates remain publicly accessible while the source repository stays private.
Developer & Governance
- Release automation now publishes with short-lived tokens from the dedicated Patchbay Release Publisher GitHub App, installed only on the public release repository with Contents write access.
- The private source workflow builds, signs, notarizes, validates, and publishes cross-repository assets without exposing source history or a reusable personal token.
Current Verification
- ✅ macOS build passed (Intel / Apple Silicon)
- ✅ TypeScript typecheck passed
Patchbay v1.29.1
Patchbay v1.29.1
发布日期:2026-07-13
发布概览
- 完成 Patchbay 独立产品身份迁移,并上线自有品牌、单仓库范围的 Patchbay Backup 连接。
用户可见更新
- Patchbay 身份完整统一 — 桌面应用、内置与独立 CLI、数据目录、数据库、锁文件、备份元数据、文档和更新路由现在只使用 Patchbay。全新安装不再携带退役产品的数据迁移路径或浏览器状态键。
- 更安全的 GitHub 备份授权 — Patchbay Backup 采用两阶段 Device Flow:第一次授权只识别用户选定的私有仓库且不保存令牌;第二次由 GitHub 签发仅限该仓库的最终令牌。公开仓库、宽范围安装和扩大后的仓库访问都会被拒绝。
- 授权变化时明确恢复 — Git 操作前和令牌刷新后都会重新验证仓库私密性与令牌范围;授权撤销或范围扩大时会显示明确的重新连接操作,不再静默退化为空凭证。
当前校验状态
- ✅ macOS Developer ID 签名和 Apple 公证通过(Intel / Apple Silicon)
- ✅ Gatekeeper 校验通过
- ✅ Updater 元数据与签名校验通过
English release notes
Release date: 2026-07-13
Release overview
- Completes Patchbay's independent product identity and introduces the branded, repository-scoped Patchbay Backup connection.
User-facing
- Patchbay identity is complete — the desktop app, bundled and standalone CLI, storage directory, database, lock files, backup metadata, documentation, and update routes now use Patchbay exclusively.
- Safer GitHub backup authorization — Patchbay Backup uses a two-stage Device Flow and rejects public repositories, broad installations, and expanded repository access.
- Clear recovery when authorization changes — repository privacy and token scope are revalidated before Git operations and after refresh.
Current verification
- ✅ Developer ID signed and Apple-notarized macOS builds (Intel / Apple Silicon)
- ✅ Gatekeeper verification passed
- ✅ Updater metadata and signatures verified