Repository navigation
chore: release 1.0.0 - #912
Merged
sunerpy merged 2 commits intoNov 19, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--pt-tools
branch
from
November 18, 2026 18:47
be87974 to
8d896e1
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--pt-tools
branch
from
November 19, 2026 00:42
8d896e1 to
8794c77
Compare
release-please 生成的 1.0.0 一节只列了 rc.60 以后的三个提交;1.0.0 是 0.48.0 之后的第一个正式版, 换成和发布 PR 正文同一份的发版说明,版本标题行保留,对比链接改成从 v0.48.0 起。
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
sunerpy
deleted the
release-please--branches--main--components--pt-tools
branch
November 19, 2026 02:53
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
1.0.0 (2026-11-19)
1.0 是 0.48.0 之后的第一个正式版,包含其间全部预览版(0.49.0-rc.1 到 rc.6、1.0.0-rc.1 到 rc.60)的改动,以及 rc.60 之后加入的飞书应用机器人与新标志。每项功能的说明见 1.0 新功能。
主要变化
从 0.48 升级
换成新的镜像或二进制直接启动:数据库结构在启动时自动迁移,迁移以前先自动备份一次(数据目录
backups/下的pt-tools-backup-<时间>-pre-upgrade.tar.gz)。这份备份没做成时照常启动和迁移,结果写在「全局设置 → 备份设置」和首页「待处理」里;想稳妥,升级前先停掉 pt-tools,自己复制一份数据目录。有几项设置在升级时自动换算:只开了做种竞争度、没开自动删种的安装会打开自动删种,只按竞争度处理;全局「免费结束自动删除」改成每条 RSS 自己选;自动删种的「免费到期仍未下完的种子自动删除」(1.0 里叫「其他免费种子免费过了没下完就删」)不再受最短保种时间限制,开着它时,加进来不满最短保种时间(默认 24 小时)的种子免费一过也会被删。详见 1.0 新功能。
要回到 0.48.0,不要直接换回旧镜像:0.48.0 没有恢复功能,会照常打开升级后的数据库,按换算后的设置运行。先停掉 pt-tools,把升级前备份里的
torrents.db与secret.key放回数据目录,删掉torrents.db-wal与torrents.db-shm,再启动 0.48.0,步骤见升级与备份。升级前备份只保留最新 3 份,要长期留着就复制到别处。Docker 的
latest标签从这一版起指向 1.0。This PR was generated with Release Please. See documentation.