docs: add Rsbuild 2.1 release blog#7991
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThe PR updates two agent skill documents and their lockfile hashes. It adds English and Chinese Rsbuild 2.1 blog posts and blog metadata, changes two Chinese guide lines, and updates the theme dark brand token to reference the main brand variable. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
Deploying rsbuild with
|
| Latest commit: |
1fe89af
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://55cf1406.rsbuild-v2.pages.dev |
| Branch Preview URL: | https://chenjiahan-docs-rsbuild-2-1.rsbuild-v2.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agents/skills/create-draft-release-notes/SKILL.md:
- Around line 75-82: The draft release command in the create-draft-release-notes
workflow always passes `--notes-start-tag` from `previous_tag`, which breaks
first releases when that value is empty. Update the `gh release create` step to
conditionally include the `--notes-start-tag` argument only when `previous_tag`
is non-empty, and keep the rest of the release creation flow in `SKILL.md`
unchanged.
- Around line 107-117: The fallback release-notes command always passes
previous_tag_name in the gh api call, which breaks when previous_tag is empty.
Update the command block in create-draft-release-notes so the generate-notes
request only includes previous_tag_name when a value is present, using the same
gh api invocation and surrounding shell variables shown in the snippet.
In `@website/docs/zh/blog/v2-1.mdx`:
- Line 88: The Chinese translation in the docs contains a duplicated “loader” in
the Tailwind CSS plugin description; update the text in the affected blog
content so the sentence uses the correct single “loader” reference only. Locate
the wording in the Tailwind CSS plugin paragraph and remove the repeated term
without changing the meaning of the description.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 1d22d051-df21-4d38-ba5e-4c9a4e8d667e
📒 Files selected for processing (10)
.agents/skills/create-draft-release-notes/SKILL.md.agents/skills/release-blog-writer/SKILL.mdskills-lock.jsonwebsite/docs/en/blog/_meta.jsonwebsite/docs/en/blog/v2-1.mdxwebsite/docs/zh/blog/_meta.jsonwebsite/docs/zh/blog/v2-1.mdxwebsite/docs/zh/guide/framework/react.mdxwebsite/docs/zh/guide/framework/solid.mdxwebsite/theme/index.scss
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1fe89af96b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Summary
Adds the release blog for Rsbuild 2.1.
Related Links
react/react#36173
https://tanstack.com/blog/start-adds-rsbuild-support