docs(release): align v0.3.0 release notes with squashed PR sources - #7
Merged
Merged
Conversation
After the squash merge of PR #6, the release range on main is the six merged pull requests #1-#6, not the original branch commits. Rewrite the v0.3.0 plan and bilingual notes to cite those PR URLs so the release audit source coverage matches, and fold the magnets behavior into PR #6's Added entry. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 25 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 上折叠）审阅者指南在 squash 合并之后，使 v0.3.0 双语发行说明和发行计划与构成 v0.2.0→v0.3.0 范围的六个 PR（#1–#6）对齐，将 magnets 行为整合到 PR #6 的单个 “Added” 条目中，并在两种语言的发行说明和发行计划 JSON 中用 PR 引用替换提交哈希。 更新后的 v0.3.0 发行说明 PR 对齐流程图flowchart LR
subgraph Sources
Commits[Commit hashes]
PRs[Pull request refs #1-#6]
end
Plan[v0.3.0 release plan JSON]
EN[English release notes v0.3.0]
ZH[Chinese release notes v0.3.0]
Commits -. previous mapping .-> EN
Commits -. previous mapping .-> ZH
PRs --> Plan
Plan --> EN
Plan --> ZH
文件级更改
提示与命令与 Sourcery 交互
自定义你的体验访问你的控制面板 以：
获取帮助Original review guide in EnglishReviewer's guide (collapsed on small PRs)Reviewer's GuideAligns the v0.3.0 bilingual release notes and release plan with the six PRs (#1–#6) that make up the v0.2.0→v0.3.0 range after a squash merge, consolidating magnets behavior into PR #6’s Added entry and replacing commit hashes with PR references in both languages and the release plan JSON. Flow diagram for updated v0.3.0 release-notes PR alignmentflowchart LR
subgraph Sources
Commits[Commit hashes]
PRs[Pull request refs #1-#6]
end
Plan[v0.3.0 release plan JSON]
EN[English release notes v0.3.0]
ZH[Chinese release notes v0.3.0]
Commits -. previous mapping .-> EN
Commits -. previous mapping .-> ZH
PRs --> Plan
Plan --> EN
Plan --> ZH
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}
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.
Summary
Release-prep for v0.3.0. After the squash merge of PR #6, the
v0.2.0...v0.3.0release range onmainis the six merged pull requests #1–#6. Rewrite the v0.3.0 plan and bilingual release notes to cite those PR URLs instead of the pre-squash branch commits, and fold the magnets behavior into PR #6'sAddedentry.Verification
sh scripts/test-releasenotes.shpasses (offline manifest + bilingual contract)go run ./scripts/releasenotes audit --from v0.2.0 --to origin/main --require-classifiedpasses (PRs docs(readme): add views badge #1–Release-notes workflow, anonymous magnets, and bilingual templates #6 classified)go run ./scripts/releasenotes validate --audit <report>passes (source coverage exact match)python -m pre_commit run --all-filespasses