Repository navigation
chore(release): version packages - #2
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (22)
💤 Files with no reviewable changes (20)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughUI 包版本从 0.2.0 更新为 0.3.0。新增 0.3.0 版本日志,并删除 20 个组件变更说明文件。 ChangesUI 包版本发布
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The 0.3.0 release metadata is consistent and ready to merge, subject to normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
🎉 Release
This PR was opened by the changesets workflow run. The
changesets/actionjob completed the versioning and pushedchangeset-release/main, but GitHub Actions is not permitted to open PRs in this organization, so it was opened manually instead.@recloudstudio/ui
0.2.0→0.3.0(minor)Changesets consumed
20 changesets were consumed by this release commit (
7cf1714).Minor
Iconcomponent — multi-library icon resolution registry (IconSource) integrated across TreeView, NavTree, CommandPalette, Tabs, CodeBlock, and menus.Patch
After merging
mainopens the Changesets Version Packages PR again only if new changesets are added.v0.3.0(exactly matchingpackages/ui/package.json) to publish to npm and GitHub Packages.The
changesets/actionfailed with:Verified via API that this is an organization-level policy, not a repo-level one:
An organization admin should enable it under:
Organization Settings → Actions → General → Workflow permissions → ☑ Allow GitHub Actions to create and approve pull requests
Until then, every push to
mainwill version successfully but be unable to open the release PR, and it will have to be opened manually.This change is
Summary by CodeRabbit