v2.4.0

[hexqi]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores
  • Upgraded version identifiers from prerelease to stable (2.4.0) across core components, plugins, and supporting packages.
  • Reintroduced a key development dependency.
  • Applied minor formatting adjustments to configuration comments.

[coderabbitai]

Walkthrough

This pull request updates version numbers across numerous package.json files from "2.4.0-rc.0" to "2.4.0", marking the transition from a release candidate to a stable release. Additionally, it reintroduces the "glob" dependency in one package and adjusts comment formatting in several environment configuration files, without affecting functionality.

Changes

File(s)	Change Summary
designer-demo/package.json, mockServer/package.json	Updated version from "2.4.0-rc.0" to "2.4.0".
packages/.../package.json (excluding common and engine-cli designer template)	Updated version from "2.4.0-rc.0" to "2.4.0".
packages/common/package.json	Updated version to "2.4.0" and reintroduced the "glob" dependency under devDependencies (version "^10.3.4").
packages/engine-cli/template/designer/package.json	Updated dependency versions (e.g. @opentiny/tiny-engine, @opentiny/tiny-engine-utils, etc.) from "2.4.0-rc.0" to "2.4.0".
packages/engine-cli/template/designer/env/.env.{alpha,development,production}	Modified comment formatting by adding a space after # in the VITE_CDN_DOMAIN comment lines.

Suggested labels

ready_for_review

Suggested reviewers

• chilingling

Poem

I'm a rabbit with a coding flair,
Skipping through updates without a care.
Bumping versions to stable and bright,
My whiskers twitch in pure delight.
Hopping through changes with a happy beat,
This PR makes my code garden complete!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a542021 and 7a2c53e.

📒 Files selected for processing (60)

• designer-demo/package.json (1 hunks)
• mockServer/package.json (1 hunks)
• packages/block-compiler/package.json (1 hunks)
• packages/blockToWebComponentTemplate/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 (2 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/env/.env.alpha (1 hunks)
• packages/engine-cli/template/designer/env/.env.development (1 hunks)
• packages/engine-cli/template/designer/env/.env.production (1 hunks)
• packages/engine-cli/template/designer/package.json (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/page/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/layout/package.json (1 hunks)
• packages/toolbars/lock/package.json (1 hunks)
• packages/toolbars/logo/package.json (1 hunks)
• packages/toolbars/logout/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/webcomponent/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: push-check

🔇 Additional comments (63)

packages/svgs/package.json (1)

1-39: Version Update Confirmation
The version number has been correctly updated to "2.4.0", marking the transition from a release candidate to a stable release. All metadata and configuration settings appear consistent.

packages/canvas/package.json (1)

1-69: Version Bump Validation
The update on line 3 to "2.4.0" is in line with the coordinated release strategy. All other settings like scripts, dependencies, and repository metadata remain intact and correctly configured.

packages/layout/package.json (1)

1-48: Stable Version Update
The package version is now set to "2.4.0", reflecting the stable release. The file remains consistent with project standards, and all configuration details continue to be correctly defined.

packages/register/package.json (1)

1-39: Consistent Version Bump
The version bump to "2.4.0" is applied correctly, aligning with similar updates across the project. The package metadata, scripts, and dependencies remain properly configured.

packages/vue-generator/package.json (1)

1-58: Coordinated Version Update
The version number update to "2.4.0" is comprehensive and consistent with the PR objectives. The configuration—including dependencies, scripts, and publishing settings—is maintained accurately.

packages/plugins/tree/package.json (1)

3-3: Version Update Verification
The version has been updated from a release candidate to a stable release ("2.4.0"). The change is consistent with similar updates in other packages.

packages/plugins/robot/package.json (1)

3-3: Stable Release Version Set
The version field is correctly updated to "2.4.0", aligning this package with the stable release across the ecosystem.

packages/plugins/state/package.json (1)

3-3: Version Bump to Stable Release
The version bump to "2.4.0" is correctly applied. Please ensure that any inter-package dependency constraints are verified with this update.

packages/plugins/block/package.json (1)

3-3: Consistent Version Update
The version update to "2.4.0" ensures that this plugin moves out of release candidate status. Dependency declarations remain consistent with the project standards.

packages/plugins/help/package.json (1)

3-3: Stable Version Confirmation
The version field is now set to "2.4.0", reflecting the transition to a stable release. All structural elements of the package.json appear to be in order.

packages/plugins/page/package.json (1)

2-3: Version Update to Stable Release.
The version number has been updated from a release candidate to the stable version "2.4.0". This aligns with the overall release objectives. Ensure related packages referencing this version are updated accordingly.

packages/block-compiler/package.json (1)

2-3: Stable Version Tag Confirmed.
The version has been correctly updated to "2.4.0". All metadata and dependency configurations are consistent with the stable release.

packages/settings/events/package.json (1)

2-3: Version Update Accurate.
The version is now "2.4.0", marking its transition from release candidate status. Verify that any consumers expecting the previous tag update their dependency specifications accordingly.

packages/plugins/materials/package.json (1)

2-3: Release Stability Update.
The version change to "2.4.0" has been applied correctly. The file’s configuration and dependency declarations now reflect the stable production release.

packages/plugins/bridge/package.json (1)

2-3: Stable Release Transition.
The update to "2.4.0" is consistent with the other packages and marks the transition from a release candidate to a stable version. Ensure all internal and external references are aligned with this change.

packages/plugins/schema/package.json (1)

3-3: Stable Release Version Update.
The version change to "2.4.0" correctly transitions this package from a release candidate to a stable release. This update aligns with the overall release strategy.

packages/settings/props/package.json (1)

3-3: Version Bump Confirmation.
The update to "2.4.0" is consistent with the objective of moving away from RC versions. Ensure that accompanying documentation and tests (if applicable) reflect this version change.

packages/settings/panel/package.json (1)

3-3: Release Candidate to Stable Transition.
Upgrading the version to "2.4.0" solidifies the package’s status as stable. This change is straightforward and meets the targeted release criteria.

packages/settings/styles/package.json (1)

3-3: Stable Version Assignment.
The version bump to "2.4.0" is appropriate for a stable release. Additionally, review the dependency list (e.g., the inclusion of "postcss": "^8.4.31") to confirm it meets compatibility requirements.

packages/plugins/tutorial/package.json (1)

3-3: Version Update for Tutorial Plugin.
The change from a release candidate version to "2.4.0" ensures consistency with the rest of the packages. Nice work keeping the versioning consistent across the repository.

packages/builtinComponent/package.json (1)

2-3: Version Update to Stable Release.
The version number has been updated from the release candidate (2.4.0-rc.0) to the stable release (2.4.0). This change is consistent with the overall PR objectives and requires no further modifications.

packages/toolbars/breadcrumb/package.json (1)

2-3: Stable Version Set.
The version field has been updated to "2.4.0", replacing the release candidate version. This aligns with the PR’s goal of finalizing the version release across packages.

packages/theme/base/package.json (1)

2-3: Consistent Version Update.
The version has been updated to "2.4.0" as part of the stabilization process. The change is clear and adheres to the coordinated version bump outlined in the PR objectives.

packages/plugins/script/package.json (2)

2-3: Version Bump to Stable Release.
The package version is now "2.4.0", transitioning from the release candidate state. This update meets the PR objectives of finalizing the release.

---

27-31: Dependency Declaration Check.
Please verify that the workspace:* dependency references are correctly resolved in the monorepo context during the build process.

packages/build/vite-plugin-meta-comments/package.json (1)

2-3: Version Update Confirmed.
The version update to "2.4.0" is correctly applied, ensuring consistency across packages as per the PR objectives.

packages/blockToWebComponentTemplate/package.json (1)

3-3: Version Bump Updated Correctly

The version number has been updated from a release candidate ("2.4.0-rc.0") to the stable release version ("2.4.0"). This update is consistent with the overall release objectives.

packages/settings/design/package.json (1)

3-3: Consistent Version Update

The package version is now updated to "2.4.0", aligning with the stable release cycle. The change is straightforward and follows the release candidate to stable upgrade.

packages/engine-cli/template/designer/env/.env.development (1)

4-4: Cosmetic Formatting Improvement

The comment on the CDN domain has been updated to include a space after the hash symbol (# VITE_CDN_DOMAIN=https://unpkg.com), which improves readability without changing functionality.

packages/engine-cli/template/designer/env/.env.alpha (1)

4-4: Consistent Comment Formatting

A similar update has been applied here by adding a space after the hash symbol in the commented VITE_CDN_DOMAIN line. This change aligns the formatting with other environment files in the repository.

packages/utils/package.json (1)

3-3: Stable Release Version Set

The version field is updated to "2.4.0", ensuring consistency with the overall stable release push across the project packages. No additional issues are observed in this change.

packages/i18n/package.json (1)

3-3: Stable Version Update Confirmed
The "version" field has been updated to "2.4.0", which correctly shifts the package from the release candidate stage to a stable release. This change is consistent with the coordinated update across other packages.

packages/engine-cli/package.json (1)

3-3: Engine-CLI Version Number Update
The version has been updated to "2.4.0". The change is straightforward and aligns with the overall project release strategy.

designer-demo/package.json (1)

4-4: Designer-Demo Version Update
The "version" field has been updated to "2.4.0". This aligns well with the coordinated stable release update across the project.

mockServer/package.json (1)

3-3: MockServer Version and Dependency Verification
The "version" field is updated to "2.4.0", ensuring consistency with the stable release rollout. Additionally, the presence of the "glob": "^10.3.4" dependency (recently reintroduced) should be verified in integration tests to confirm it meets the required use cases.

packages/plugins/datasource/package.json (1)

3-3: Datasource Plugin Version Update
The package version has been updated to "2.4.0", which is in line with the stable release transition observed across the ecosystem.

packages/toolbars/clean/package.json (1)

3-3: Stable Version Update in Toolbar Clean Package
The version field is updated to "2.4.0", which aligns with the intended transition from a release candidate to a stable release.

packages/plugins/i18n/package.json (1)

3-3: Stable Version Update in Plugin I18n Package
Updating the version to "2.4.0" here is consistent with the overall release objective. No extraneous changes were made in this hunk.

packages/configurator/package.json (1)

3-3: Stable Version Update in Configurator Package
The version update to "2.4.0" correctly reflects the transition from a release candidate to a stable release. Ensure that any dependent tools or packages referencing this package are updated accordingly.

packages/webcomponent/package.json (1)

3-3: Stable Version Update in Webcomponent Core Package
The update to "2.4.0" maintains consistency for a stable release. The rest of the configuration appears unchanged and well-configured.

packages/toolbars/redoundo/package.json (1)

3-3: Stable Version Update in Toolbar Redoundo Package
The version is updated to "2.4.0", which is consistent with the coordinated stable release for all related packages.

packages/toolbars/media/package.json (1)

3-3: Stable Release Version Update:
The version number has been updated from a release candidate (2.4.0-rc.0) to a stable release (2.4.0), which aligns perfectly with the project’s goal of stabilizing this package.

packages/toolbars/lock/package.json (1)

3-3: Stable Release Version Update:
The version field is correctly modified to 2.4.0, ensuring consistency across the project as the package transitions from RC to stable.

packages/toolbars/lang/package.json (1)

3-3: Stable Release Version Update:
The version bump to 2.4.0 is correctly applied. The JSON structure remains valid and consistent with the broader coordinated release effort.

packages/toolbars/save/package.json (1)

3-3: Stable Release Version Update:
This change updates the version from a release candidate to a stable release (2.4.0), and the modification follows the standard format seen across similar packages.

packages/toolbars/refresh/package.json (1)

3-3: Stable Release Version Update:
The update of the version field to 2.4.0 is properly executed here, matching the stabilization efforts seen in other packages. This maintains overall consistency in the project’s versioning scheme.

packages/toolbars/logout/package.json (1)

3-3: Version Bump to Stable Release
The version number is correctly updated from a release candidate format to a stable release ("2.4.0"). Please ensure that associated documentation and changelogs reflect this change.

packages/toolbars/layout/package.json (1)

3-3: Version Update Confirmed
The version has been updated to "2.4.0" in this package, aligning with your coordinated release across packages. Make sure that any references to version numbers in related configuration or dependency documentation are also updated if necessary.

packages/build/vite-config/package.json (1)

3-3: Consistent Version Bump
The update to "2.4.0" here reinforces the project’s move out of the release candidate phase. Confirm that this change does not introduce inconsistencies in dependency resolution and all build scripts referring to this package are using the correct stable version.

packages/toolbars/preview/package.json (1)

3-3: Stable Release Version Set
Updating the version number to "2.4.0" successfully transitions the package to a stable release. Please verify that any linked package references or automated tooling that depends on version strings are updated accordingly.

packages/toolbars/setting/package.json (1)

3-3: Transition to Stable Version
The version bump to "2.4.0" is correctly applied here. Ensure that external dependencies or projects referencing this package are aware of the version change, and update any relevant changelog or release notes.

packages/toolbars/fullscreen/package.json (1)

3-3: Stable Version Update:
The version has been updated to "2.4.0", reflecting the transition from a release candidate to a stable release. This is consistent with the overall release process outlined in the PR objectives.

packages/toolbars/themeSwitch/package.json (1)

3-3: Version Update to Stable Release:
The version number change to "2.4.0" is correctly applied, ensuring alignment with the coordinated stabilization effort across multiple packages.

packages/toolbars/generate-code/package.json (1)

3-3: Stable Release Version Applied:
The version has been updated to "2.4.0", effectively marking the package as a stable release rather than a release candidate. This update is consistent with the project's release strategy.

packages/toolbars/collaboration/package.json (1)

3-3: Release Candidate to Stable Transition:
The updated version "2.4.0" confirms the package’s move to a stable release state. This change aligns with the broader effort of synchronizing version numbers across the project.

packages/toolbars/logo/package.json (1)

3-3: Stable Version Number Updated:
The version number update to "2.4.0" properly signifies the transition out of the release candidate phase. The change is consistent with similar updates in other packages.

packages/toolbars/view-setting/package.json (1)

3-3: Version Update Confirmed.
The version number has been updated from a release candidate to the stable release version ("2.4.0"), which aligns with the overall release stabilization effort.

packages/design-core/package.json (1)

3-3: Stable Version Update.
The package version has been correctly updated to "2.4.0", ensuring consistency with the stable release across the project.

packages/engine-cli/template/designer/env/.env.production (1)

4-4: Consistent Comment Formatting.
The commented VITE_CDN_DOMAIN now includes a space after the "#" symbol, which improves readability without affecting functionality.

packages/common/package.json (2)

2-4: Package Version Updated.
The version has been updated from its prior release candidate form to "2.4.0", matching the stabilized release version.

---

54-54: Dependency Reinstatement Confirmed.
The "glob": "^10.3.4" dependency has been reintroduced in devDependencies, ensuring that any development tools relying on it will function correctly.

packages/engine-cli/template/designer/package.json (2)

14-15: Stable Dependency Versions.
The dependencies @opentiny/tiny-engine and @opentiny/tiny-engine-utils have been updated to "2.4.0" from their previous RC versions, ensuring consistency across the repository.

---

26-27: Aligned Dev Dependency Versions.
The devDependencies @opentiny/tiny-engine-mock and @opentiny/tiny-engine-vite-config have been updated to the stable release "2.4.0", ensuring alignment with the stable release rollout.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.