Repository navigation
chore: 发布 1.5.0 - #7
Merged
Merged
Conversation
变更范围（相对 1.4.0）： - feat: provider 工厂统一、Responses 协议面、local-hash 离线嵌入（PR #1） - chore: ruff format 全仓套用（PR #2） - fix: 检索与快照边界硬化——变异审计工具链收口 + 九轮 agents 审查 + codex 全 diff 复核，40 处缺陷与 12 处卫生问题（PR #3） - feat: main.py 支持 -h/--help（PR #4）；TUI 提示色亮/暗主题适配（PR #5） - docs: 命令行参数与主题适配说明（PR #6） 测试 4185 → 4547，全部红/绿验证。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
审查者指南（小型 PR 中折叠显示）审查者指南本次发布准备通过同步更新项目元数据和 CHANGELOG，将版本从 1.4.0 提升至 1.5.0；合并后需创建 v1.5.0 tag 以触发五平台 release workflow 构建。 文件级变更
提示和命令使用 Sourcery
自定义使用体验访问你的控制面板以：
获取帮助Original review guide in EnglishReviewer's guide (collapsed on small PRs)Reviewer's Guide本次发布准备通过同步更新项目元数据和 CHANGELOG，将版本从 1.4.0 提升至 1.5.0；合并后需创建 v1.5.0 tag 以触发五平台 release workflow 构建。 File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
嗨——我发现了 3 个问题
面向 AI 代理的提示
请处理此代码审查中的评论：
## 单条评论
### 评论 1
<location path="pyproject.toml" line_range="3" />
<code_context>
[project]
name = "pyrag-kit"
-version = "1.4.0"
+version = "1.5.0"
description = "A lightweight Python implementation of Dify core RAG logic"
readme = "README.md"
</code_context>
<issue_to_address>
**发布测试失败**
项目版本号更新后运行 `tests/test_release_scripts.py::test_validate_bundle_uses_smoke_test` 时，`validate_bundle` 会将冒烟测试的输出与 `load_version()`（现在是 1.5.0）进行比较，但此测试中的模拟可执行文件报告的是 1.4.0，因此 pytest 会失败并阻止发布。
请将模拟的冒烟测试输出更新为当前项目版本，或改为动态获取版本号。
</issue_to_address>
### 评论 2
<location path="CHANGELOG.md" line_range="5" />
<code_context>
所有此项目的显著更改都将记录在此文件中。
-## [Unreleased]
+## [1.5.0] - 2026-10-15
### 新增
</code_context>
<issue_to_address>
**未来更改会被纳入已发布版本的说明**
如果贡献者在本次发布之后、添加下一个版本标题之前提交更改，`extract_section("1.5.0")` 会一直包含后续条目，直到遇到下一个版本标题。因此，在当前唯一的标题下添加的发布后更改，会出现在 1.5.0 版本说明中，仿佛已经发布。
请在 1.5.0 条目上方恢复 `## [Unreleased]` 部分。
</issue_to_address>
### 评论 3
<location path="pyproject.toml" line_range="3" />
<code_context>
[project]
name = "pyrag-kit"
-version = "1.4.0"
+version = "1.5.0"
description = "A lightweight Python implementation of Dify core RAG logic"
readme = "README.md"
</code_context>
<issue_to_address>
**路线图中当前版本仍是旧版本**
开发者在此次版本号更新后查阅路线图时，会看到路线图称变更日志的当前版本为 1.4.0。因此，按照该指引操作的开发者会使用过时的发布基准版本。
请将路线图中的当前版本引用更新为 1.5.0。
</issue_to_address>Sourcery 评估
等待批准。 请先处理 2 项发现。
阻塞性发现：pyproject.toml:3、CHANGELOG.md:5
Original comment in English
Hey - I've found 3 issues
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="pyproject.toml" line_range="3" />
<code_context>
[project]
name = "pyrag-kit"
-version = "1.4.0"
+version = "1.5.0"
description = "A lightweight Python implementation of Dify core RAG logic"
readme = "README.md"
</code_context>
<issue_to_address>
**Release tests fail**
When `tests/test_release_scripts.py::test_validate_bundle_uses_smoke_test` runs after the project version is bumped, `validate_bundle` compares the smoke-test output with `load_version()` (now 1.5.0), but this test’s fake executable reports 1.4.0, so pytest fails and blocks release publishing.
Update the stubbed smoke-test output to use the current project version, or derive it dynamically.
</issue_to_address>
### Comment 2
<location path="CHANGELOG.md" line_range="5" />
<code_context>
所有此项目的显著更改都将记录在此文件中。
-## [Unreleased]
+## [1.5.0] - 2026-10-15
### 新增
</code_context>
<issue_to_address>
**Future changes enter released notes**
When contributors add changes after this release but before adding the next version heading, `extract_section("1.5.0")` includes subsequent entries until the next version heading, so post-release changes added under the only current heading appear in the 1.5.0 release notes as already released.
Restore an `## [Unreleased]` section above the 1.5.0 entry.
</issue_to_address>
### Comment 3
<location path="pyproject.toml" line_range="3" />
<code_context>
[project]
name = "pyrag-kit"
-version = "1.4.0"
+version = "1.5.0"
description = "A lightweight Python implementation of Dify core RAG logic"
readme = "README.md"
</code_context>
<issue_to_address>
**Roadmap names old current version**
When a developer consults the roadmap after this version bump, the roadmap says the changelog's current version is 1.4.0, so developers following that pointer get an outdated release baseline.
Update the roadmap's current-version reference to 1.5.0.
</issue_to_address>Sourcery assessment
Approval pending. 2 findings to address first.
Blocking findings: pyproject.toml:3, CHANGELOG.md:5
| 所有此项目的显著更改都将记录在此文件中。 | ||
|
|
||
| ## [Unreleased] | ||
| ## [1.5.0] - 2026-10-15 |
There was a problem hiding this comment.
🟡 Medium · 未来更改会被纳入已发布版本的说明
如果贡献者在本次发布之后、添加下一个版本标题之前提交更改，extract_section("1.5.0") 会一直包含后续条目，直到遇到下一个版本标题。因此，在当前唯一的标题下添加的发布后更改，会出现在 1.5.0 版本说明中，仿佛已经发布。
请在 1.5.0 条目上方恢复 ## [Unreleased] 部分。
面向 AI 代理的提示
在 `CHANGELOG.md` 第 5 行：
**未来更改会被纳入已发布版本的说明**
如果贡献者在本次发布之后、添加下一个版本标题之前提交更改，`extract_section("1.5.0")` 会一直包含后续条目，直到遇到下一个版本标题。因此，在当前唯一的标题下添加的发布后更改，会出现在 1.5.0 版本说明中，仿佛已经发布。
请在 1.5.0 条目上方恢复 `## [Unreleased]` 部分。Original comment in English
🟡 Medium · Future changes enter released notes
When contributors add changes after this release but before adding the next version heading, extract_section("1.5.0") includes subsequent entries until the next version heading, so post-release changes added under the only current heading appear in the 1.5.0 release notes as already released.
Restore an ## [Unreleased] section above the 1.5.0 entry.
Prompt for AI agents
In `CHANGELOG.md` at line 5:
**Future changes enter released notes**
When contributors add changes after this release but before adding the next version heading, `extract_section("1.5.0")` includes subsequent entries until the next version heading, so post-release changes added under the only current heading appear in the 1.5.0 release notes as already released.
Restore an `## [Unreleased]` section above the 1.5.0 entry.| [project] | ||
| name = "pyrag-kit" | ||
| version = "1.4.0" | ||
| version = "1.5.0" |
There was a problem hiding this comment.
⚪ Low · 路线图中当前版本仍是旧版本
开发者在此次版本号更新后查阅路线图时，会看到路线图称变更日志的当前版本为 1.4.0。因此，按照该指引操作的开发者会使用过时的发布基准版本。
请将路线图中的当前版本引用更新为 1.5.0。
面向 AI 代理的提示
在 `pyproject.toml` 第 3 行：
**路线图中当前版本仍是旧版本**
开发者在此次版本号更新后查阅路线图时，会看到路线图称变更日志的当前版本为 1.4.0。因此，按照该指引操作的开发者会使用过时的发布基准版本。
请将路线图中的当前版本引用更新为 1.5.0。Original comment in English
⚪ Low · Roadmap names old current version
When a developer consults the roadmap after this version bump, the roadmap says the changelog's current version is 1.4.0, so developers following that pointer get an outdated release baseline.
Update the roadmap's current-version reference to 1.5.0.
Prompt for AI agents
In `pyproject.toml` at line 3:
**Roadmap names old current version**
When a developer consults the roadmap after this version bump, the roadmap says the changelog's current version is 1.4.0, so developers following that pointer get an outdated release baseline.
Update the roadmap's current-version reference to 1.5.0.test_validate_bundle_uses_smoke_test 的替身输出硬编码 1.4.0， 升版本到 1.5.0 后触发守卫「发布包自报版本与 pyproject.toml 不一致」 （CI 实测）。改为从 load_version() 动态构造——该守卫拦的正是这种 漂移，夹具不能自己复现它。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
版本号 1.4.0 → 1.5.0，CHANGELOG Unreleased 归档为 [1.5.0] - 2026-10-15。合并后打
v1.5.0tag 触发 release workflow 构建五平台产物。🤖 Generated with Claude Code
Sourcery 总结
为项目的 1.5.0 版本发布做好准备。
文档：
杂项：
Original summary in English
Sourcery 摘要
为项目发布 1.5.0 版本做好准备。
增强功能：
文档：
测试：
Original summary in English
Summary by Sourcery
Prepare the project for the 1.5.0 release.
Enhancements:
Documentation:
Tests: