Repository navigation
v0.7.5
What's New in v0.7.5
Version 0.7.5 improves release tracking, vector-search reliability, version management, and synchronization with GitHub Lists.
Highlights
Release and version management
- Centralized application versioning (PR #270): the root
package.jsonis now the single source of truth for the app version. The lockfile is synchronized automatically, the duplicate Electron version field was removed, and the release helper now rejects duplicate or downgraded versions while validating metadata and download URLs more safely.
Vector-search reliability
-
Safer Vectorize metadata handling (PR #271): vector metadata is now compacted at the Cloudflare Worker
/upsertboundary using UTF-8 JSON byte limits. Oversized descriptions and tags, malformed license metadata, and excessive similarity-search limits are handled safely instead of failing.[!IMPORTANT]
If you use the Cloudflare Worker deployment, redeploy the Worker before using this fix.
Release update tracking
- Improved release refresh behavior (PR #272): when a release's assets or metadata change, the release is correctly marked as unread again. Displayed timestamps now reflect the latest asset update, and affected releases show an
Assets updatedindicator while the read state of unaffected releases is preserved. - Clearer asset-update indicators (PR #274): the
Assets updatedindicator now disappears when the release is marked as read. The behavior is consistent in both release cards and repository group headers, with extra coverage for timestamp and read-state edge cases.
GitHub Lists synchronization
-
Experimental two-way GitHub Lists synchronization (PR #273, addressing issue #229): you can optionally pull GitHub native Lists into the app and push local categories back to GitHub Lists. The feature supports configurable sync modes, protected categories, list-to-tag/category mapping, and confirmation dialogs before anything can be overwritten.
[!WARNING]
This is an experimental feature — please back up your data before trying it. Existing users, and users who do not use GitHub native Lists, are advised to stay on the legacy synchronization mode. GitHub Lists synchronization is optional and can be selected in the sync settings.
Upgrade notes
After upgrading, users of the Cloudflare Worker deployment must redeploy the Worker for the vector-search fix (PR #271) to take effect. If you want to try GitHub Lists synchronization, back up your data first; you can keep using the legacy synchronization mode if you don't need native Lists support.
v0.7.5 更新内容
0.7.5 改进了 Release 跟踪、向量搜索的稳定性、版本管理,以及与 GitHub Lists 的同步。
主要亮点
Release 与版本管理
- 应用版本统一管理(PR #270):根目录
package.json现在是应用版本的唯一来源。lockfile 自动同步,移除了重复的 Electron 版本字段,发版脚本会拒绝重复或降级的版本号,并对元数据和下载链接做更严格的安全校验。
向量搜索稳定性
-
更安全的 Vectorize 元数据处理(PR #271):向量元数据现在在 Cloudflare Worker 的
/upsert边界按 UTF-8 JSON 字节数上限进行压缩。过长的描述和标签、格式错误的 License 元数据、过大的相似搜索上限都会被安全处理,而不再导致失败。[!IMPORTANT]
如果你在用 Cloudflare Worker 部署,请先重新部署 Worker,此修复才会生效。
Release 更新跟踪
- Release 刷新行为改进(PR #272):当 Release 的资产或元数据发生变化时,会重新正确地标为未读。显示的时间戳反映最新的资产更新时间,受影响的 Release 会显示
Assets updated提示,未受影响 Release 的已读状态保持不变。 - 更清晰的资产更新提示(PR #274):Release 标为已读后
Assets updated提示随之消失。该行为在 Release 卡片和仓库分组头部保持一致,并补充了时间戳与已读状态的边界情况处理。
GitHub Lists 同步
-
实验性的 GitHub Lists 双向同步(PR #273,对应 issue #229):可以选择把 GitHub 原生 Lists 拉取到应用内,也可以把本地分类推送回 GitHub Lists。支持可配置的同步模式、受保护分类、List 与标签/分类的映射,以及可能覆盖数据前的确认弹窗。
[!WARNING]
这是实验性功能——试用前请先备份数据。 老用户以及不使用 GitHub 原生 Lists 的用户,建议继续使用旧同步模式。GitHub Lists 同步是可选项,可在同步设置中开启。
升级说明
升级后,使用 Cloudflare Worker 部署的用户需要重新部署 Worker,向量搜索修复(PR #271)才能生效。想尝试 GitHub Lists 同步的用户请先备份数据;不需要原生 Lists 支持的话,可以继续使用旧同步模式。
Desktop Downloads / 桌面端下载
This release includes installers for Windows, macOS, and Linux. Use the Assets section below to download the package for your platform.
本版本提供 Windows、macOS 和 Linux 安装包,见下方 Assets。