Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@ SubBoost v2.5.0 主要改善代理组编辑、自部署更新和订阅生成稳

### 主要变化

- 新增高级代理组模式,自定义分组、规则集和手动规则的编辑状态会更稳定地保存
- 自定义代理组入口更统一,可以更方便地按来源、地区、关键词和排除条件整理节点。
- 移除单独的筛选代理组入口,相关功能转移到分流代理组高级模式和自定义分流组
- 分流代理组高级模式支持按来源、地区、关键词和排除条件整理节点。
- 订阅生成更稳,规则顺序、代理组输出和常见 Mihomo 字段处理减少了意外变化。
- 节点导入兼容性更好,覆盖更多常见节点链接和 Clash/Mihomo YAML 配置。
- 节点导入兼容性更好,覆盖更多常见节点链接和 Mihomo YAML 配置。
- 自部署安装和更新流程更可靠,`subboost update`、状态检查和失败提示都有改进。
- Dashboard 下载订阅 YAML 的行为更接近直接访问订阅链接,文件名和响应头更稳定。
- 首次安装后的管理员初始化、登录和数据库连接更稳,减少安装完成后进不去后台的情况。
Expand All @@ -22,7 +22,7 @@ SubBoost v2.5.0 主要改善代理组编辑、自部署更新和订阅生成稳
- 建议升级前备份 `/opt/subboost/.env` 和数据库,方便需要时回滚。
- 已安装 v2.4.0 的自部署实例可以继续使用 `subboost update` 更新。
- 普通订阅转换、模板和规则功能不需要手动改环境变量。
- 如果你在 v2.4.0 使用过筛选代理组,请升级后打开自定义代理组检查输出结果;必要时用新的高级代理组重新配置
- 现有筛选代理组会自动迁移到自定义代理组。如果你在 v2.4.0 使用过筛选代理组,请升级后打开自定义代理组检查;必要时可能需要重新配置

## English

Expand All @@ -32,10 +32,10 @@ SubBoost v2.5.0 mainly improves proxy group editing, self-hosted updates, and su

### Main Changes

- Added advanced proxy group mode, with more reliable persistence for custom groups, rule sets, and manual rules.
- Unified the custom proxy group entry point, making it easier to organize nodes by source, region, keyword, and exclusion rules.
- Removed the separate filtered proxy group entry point. Related features have moved to proxy group advanced mode and custom proxy groups.
- Proxy group advanced mode supports organizing nodes by source, region, keyword, and exclusion rules.
- Made subscription generation more stable, reducing unexpected changes in rule order, proxy group output, and common Mihomo fields.
- Improved node import compatibility for more common node links and Clash/Mihomo YAML configurations.
- Improved node import compatibility for more common node links and Mihomo YAML configurations.
- Made self-hosted install and update flows more reliable, including `subboost update`, status checks, and failure messages.
- Dashboard YAML downloads now behave more like direct subscription links, with steadier filenames and response headers.
- Improved first-install admin setup, login, and database connection reliability to reduce post-install access issues.
Expand All @@ -46,4 +46,4 @@ SubBoost v2.5.0 mainly improves proxy group editing, self-hosted updates, and su
- Back up `/opt/subboost/.env` and the database before upgrading so rollback is easier if needed.
- Existing v2.4.0 self-hosted installations can continue to update with `subboost update`.
- Normal subscription conversion, templates, and rules do not require manual environment-variable changes.
- If you used filtered proxy groups in v2.4.0, open the custom proxy group editor after upgrading and check the generated output. Recreate those groups with the new advanced proxy group controls if needed.
- Existing filtered proxy groups will migrate to custom proxy groups automatically. If you used filtered proxy groups in v2.4.0, open the custom proxy group editor after upgrading and check the result. You may need to reconfigure them if the output is not what you expect.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Do not promise automatic filtered-group migration

This is not currently true for v2.4 configs that still contain the legacy filteredProxyGroups field: repo-wide search only finds that field in the removed-template-field list/docs, validateSubBoostTemplateConfig rejects it as removed (packages/core/src/templates/config-template.ts:33-38), and the generation normalizers build groups from customProxyGroups rather than migrating filteredProxyGroups (packages/core/src/rules/rule-model.ts:105-120, packages/core/src/subscription/config-utils.ts:247-251). Users relying on this upgrade note may skip manually recreating or exporting filtered groups and then find those groups missing after upgrade.

Useful? React with 👍 / 👎.