Skip to content

v2.4.1-rc.0#1333

Closed
chilingling wants to merge 1 commit intoopentiny:release/v2.4.xfrom
chilingling:v2.4.1-rc.0
Closed

v2.4.1-rc.0#1333
chilingling wants to merge 1 commit intoopentiny:release/v2.4.xfrom
chilingling:v2.4.1-rc.0

Conversation

@chilingling
Copy link
Member

@chilingling chilingling commented Apr 24, 2025

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
    • Updated the version number to 2.4.1-rc.0 across multiple packages to reflect a new release candidate.
    • No changes to features, user interface, or functionality.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 24, 2025

Walkthrough

This change updates the version field in multiple package.json files across the repository, incrementing each package's version from 2.4.0 to the pre-release version 2.4.1-rc.0. No other modifications to dependencies, scripts, configuration, or code are present. The update is limited strictly to metadata, with no impact on exported or public entities.

Changes

Files (Grouped) Change Summary
All package.json files across designer-demo/, mockServer/, packages/*/, and subpackages Updated the version field from 2.4.0 to 2.4.1-rc.0. No other changes to dependencies, scripts, configuration, or code.

Possibly related PRs

  • v2.0.0 #934: Also updates package version fields in multiple package.json files, indicating a sequential version bump.
  • v2.5.0-alpha.2 #1315: Exclusively updates package version numbers in multiple package.json files without code changes, similar in purpose.
  • v2.4.0 #1287: Updates the same package versions but in the opposite direction (from release candidate to stable), modifying only version metadata.

Suggested labels

ignore-for-release

Poem

The numbers leap, the carrots grow,
From 2.4.0 to rc we go!
No code was changed, no scripts were run,
Just version tags—now isn’t that fun?
With every hop, the garden’s neat,
Release is near, the cycle’s sweet.
🥕✨


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
🪧 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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ae2317f and 201b935.

📒 Files selected for processing (56)
  • 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 (1 hunks)
  • packages/configurator/package.json (1 hunks)
  • packages/design-core/package.json (1 hunks)
  • packages/engine-cli/package.json (1 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)
🧰 Additional context used
🧠 Learnings (19)
packages/canvas/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/layout/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/bridge/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/schema/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/webcomponent/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/help/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/tutorial/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/svgs/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/script/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/engine-cli/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/tree/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/plugins/state/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/block-compiler/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/configurator/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/utils/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/design-core/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/vue-generator/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/common/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
packages/builtinComponent/package.json (1)
Learnt from: gene9831
PR: opentiny/tiny-engine#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.
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: push-check
🔇 Additional comments (55)
packages/theme/base/package.json (1)

3-3: Consistent version bump to v2.4.1-rc.0
The version field was correctly updated from 2.4.02.4.1-rc.0, matching the release candidate tagging across the project.

packages/common/package.json (1)

3-3: Consistent version bump to v2.4.1-rc.0
The version field was updated in line with the coordinated RC release across all packages.

packages/svgs/package.json (1)

3-3: Consistent version bump to v2.4.1-rc.0
This change aligns the SVGs package with the RC versioning strategy applied throughout the monorepo.

packages/register/package.json (1)

3-3: Consistent version bump to v2.4.1-rc.0
The metadata version has been correctly updated for the meta-register package.

packages/builtinComponent/package.json (1)

3-3: Consistent version bump to v2.4.1-rc.0
The built-in component package now reflects the RC tag, in sync with the rest of the project.

packages/utils/package.json (1)

3-3: Bump version to pre-release 2.4.1-rc.0.
Aligned with the coordinated version update across the repo.

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

3-3: Bump version to pre-release 2.4.1-rc.0.
Consistent with the other packages’ version updates in this release candidate.

packages/layout/package.json (1)

3-3: Bump version to pre-release 2.4.1-rc.0.
Maintains uniform versioning for the layout package in this RC.

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

3-3: Bump version to pre-release 2.4.1-rc.0.
Matches the global version bump across all plugins.

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

3-3: Bump version to pre-release 2.4.1-rc.0.
Ensures the generate-code toolbar aligns with the RC version scheme.

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

3-3: Consistent version bump applied
The version field has been correctly updated to 2.4.1-rc.0, aligning this package with the release candidate.

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

3-3: Release candidate version matched
The version field update to 2.4.1-rc.0 is correct and keeps this plugin in sync with the rest of the packages.

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

3-3: Version update verified
This package’s version has been bumped to 2.4.1-rc.0 consistently with the other toolbar modules.

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

3-3: Correct RC version set
The version field now reflects 2.4.1-rc.0, matching the coordinated release candidate across the build plugins.

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

3-3: Release candidate version alignment
Updated version to 2.4.1-rc.0 to maintain consistency with the other toolbar packages.

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

3-3: Upgrade package version to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Upgrade package version to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Upgrade package version to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Upgrade package version to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Upgrade package version to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Consistent version bump to 2.4.1-rc.0
The version field has been updated from 2.4.0 to the pre-release candidate 2.4.1-rc.0, matching the coordinated versioning strategy across all packages. No other metadata changes detected.

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

3-3: Consistent version bump to 2.4.1-rc.0
The version field has been updated from 2.4.0 to the pre-release candidate 2.4.1-rc.0, aligning with the repository-wide release candidate update.

packages/canvas/package.json (1)

3-3: Consistent version bump to 2.4.1-rc.0
Updated the version from 2.4.0 to 2.4.1-rc.0 in @opentiny/tiny-engine-canvas to match the coordinated release candidate versioning.

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

3-3: Consistent version bump to 2.4.1-rc.0
The plugin package’s version field has been updated from 2.4.0 to 2.4.1-rc.0, ensuring consistency with the rest of the repository.

packages/webcomponent/package.json (1)

3-3: Consistent version bump to 2.4.1-rc.0
The core webcomponent package has its version field updated from 2.4.0 to 2.4.1-rc.0, in line with the repository-wide release candidate rollout.

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

3-3: Consistent version bump to 2.4.1-rc.0
The "version" field has been correctly updated from 2.4.0 to the release candidate 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Consistent version bump to 2.4.1-rc.0
The "version" field has been correctly updated from 2.4.0 to the release candidate 2.4.1-rc.0. No other metadata changes detected.

designer-demo/package.json (1)

4-4: Consistent version bump to 2.4.1-rc.0
The "version" field has been correctly updated from 2.4.0 to the release candidate 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Consistent version bump to 2.4.1-rc.0
The "version" field has been correctly updated from 2.4.0 to the release candidate 2.4.1-rc.0. No other metadata changes detected.

packages/configurator/package.json (1)

3-3: Consistent version bump to 2.4.1-rc.0
The "version" field has been correctly updated from 2.4.0 to the release candidate 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Version bump to 2.4.1-rc.0
The package version has been updated from 2.4.0 to the pre-release 2.4.1-rc.0, which aligns with the coordinated release candidate tagging across all packages.

packages/blockToWebComponentTemplate/package.json (1)

3-3: Version bump to 2.4.1-rc.0
Updated the version field to 2.4.1-rc.0, consistent with the rest of the mono-repo’s release candidate update.

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

3-3: Version bump to 2.4.1-rc.0
The CLI package version has been updated to the pre-release 2.4.1-rc.0. Please ensure any user-facing documentation or example scripts referencing the CLI version are updated accordingly.

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

3-3: Version bump to 2.4.1-rc.0
The toolbar-save package version is now 2.4.1-rc.0, matching the global release candidate.

mockServer/package.json (1)

3-3: Version bump to 2.4.1-rc.0
Updated mock-server package version to 2.4.1-rc.0, in line with the overall release candidate rollout.

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

3-3: Consistent version bump applied. The version field has been correctly updated from 2.4.0 to 2.4.1-rc.0. No other metadata changes detected.

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

3-3: Version updated correctly. The @opentiny/tiny-engine-plugin-schema package version has been bumped from 2.4.0 to 2.4.1-rc.0 in line with the release candidate.

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

3-3: Release candidate version set. The version field has been updated to 2.4.1-rc.0 consistently with the PR objective.

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

3-3: Version bump is correct. The package version for @opentiny/tiny-engine-toolbar-logo has been updated to 2.4.1-rc.0 as expected.

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

3-3: Correct pre-release version. The version field now reflects 2.4.1-rc.0 to align with the intended release candidate across the project.

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

3-3: Approve version update to 2.4.1-rc.0
The version field has been correctly bumped from 2.4.0 to the pre-release 2.4.1-rc.0, aligning with the coordinated release candidate across all packages.

packages/i18n/package.json (1)

3-3: Approve version update to 2.4.1-rc.0
The version field has been updated to the pre-release 2.4.1-rc.0, ensuring consistency with the global version bump in this release candidate.

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

3-3: Approve version update to 2.4.1-rc.0
The version has been bumped to 2.4.1-rc.0 as part of the release candidate roll-out, with no other metadata changes.

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

3-3: Approve version update to 2.4.1-rc.0
This package’s version field correctly reflects the pre-release 2.4.1-rc.0, matching the project-wide release candidate standard.

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

3-3: Approve version update to 2.4.1-rc.0
The version has been updated from 2.4.0 to the RC tag 2.4.1-rc.0 as expected, with no unintended side-effects.

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

3-3:

Details

✅ Verification successful

Verify and approve version bump to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0, matching the coordinated bump across the repository.

To confirm no stale 2.4.0 remains in any package manifest, run:


🏁 Script executed:

#!/bin/bash
# Description: Ensure all package.json files use the new pre-release version and none retain the old version.

# Fail if any package.json still contains the old version
if rg -l '"version": "2.4.0"' -g 'packages/**/*.json'; then
  echo "Error: Found stale version 2.4.0 in package.json"
  exit 1
fi

# Report how many packages were updated
updated_count=$(rg -c '"version": "2.4.1-rc.0"' -g 'packages/**/*.json' | wc -l)
echo "Packages updated to 2.4.1-rc.0: $updated_count"

Length of output: 218


Version bump verified: All package.json files updated to 2.4.1-rc.0
No stale "2.4.0" entries were found; 54 packages now reflect "2.4.1-rc.0".

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

3-3: Approved: Version bump to 2.4.1-rc.0
This package.json correctly reflects the new release candidate version, consistent with other packages.

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

3-3: Approved: Version bump to 2.4.1-rc.0
The version update aligns with the project-wide pre-release roll-out.

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

3-3: Approved: Version bump to 2.4.1-rc.0
Maintains consistency with the overall release candidate versioning strategy.

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

3-3: Approved: Version bump to 2.4.1-rc.0
Aligned with the coordinated version update across all Tiny Engine packages.

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

3-3: Version bump to 2.4.1-rc.0
The version field has been correctly updated from 2.4.0 to the pre-release 2.4.1-rc.0, maintaining consistency with the release candidate workflow.

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

3-3: Version bump to 2.4.1-rc.0
The version field has been updated consistently with the rest of the repo’s packages for the 2.4.1-rc.0 release.

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

3-3: Version bump to 2.4.1-rc.0
Pre-release version tag applied correctly; no other metadata was altered.

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

3-3: Version bump to 2.4.1-rc.0
Release candidate version string updated in line with the global version upgrade.

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

3-3: Version bump to 2.4.1-rc.0
Version field updated to the 2.4.1-rc.0 pre-release across all plugin packages.

{
"name": "@opentiny/tiny-engine-plugin-state",
"version": "2.4.0",
"version": "2.4.1-rc.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Version bump is correct
The version field has been updated from 2.4.0 to 2.4.1-rc.0 as expected for the release candidate. Please verify that this pre-release version is applied consistently across all package.json files to avoid mismatches.


🏁 Script executed:

#!/bin/bash
# Verify consistent version across all package.json files
expected='"version": "2.4.1-rc.0"'
rg -l '"version": ' --glob 'packages/**/package.json' | while read -r file; do
  if ! grep -q "$expected" "$file"; then
    echo "Version mismatch in $file"
    exit 1
  fi
done
echo "All package.json versions are consistent."

Length of output: 1255


Exclude test fixtures from version check
The only mismatch comes from packages/vue-generator/test/testcases/element-plus-case/expected/appdemo01/package.json, which is a test snapshot and shouldn’t be included in the release version check. Please refine your verification script to skip test directories.

– Modify the grep command to ignore packages/**/test/** (or specifically the testcases folder)
– Ensure all actual package.json files still match "version": "2.4.1-rc.0"

Example updated script:

#!/bin/bash
expected='"version": "2.4.1-rc.0"'
rg -l '"version": ' --glob 'packages/**/package.json' --glob '!packages/**/test/**' | while read -r file; do
  if ! grep -q "$expected" "$file"; then
    echo "Version mismatch in $file"
    exit 1
  fi
done
echo "All non-test package.json versions are consistent."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant