Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/mock utils axios cdn link #1062

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

yy-wow
Copy link
Collaborator

@yy-wow yy-wow commented Jan 22, 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?

本地启动mock服务有报错
image

Issue Number: N/A

What is the new behavior?

正常加载utils,无报错

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Chores
    • Updated CDN link for axios utility to remove /browse/ segment
    • Simplified external resource URL configuration

Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

Walkthrough

This pull request involves a comprehensive version update across multiple packages from version 2.1.0 to 2.2.0-rc.0, indicating a release candidate phase. The changes span numerous packages within the project, including core components, plugins, toolbars, and utilities. Additionally, there are minor modifications to workflow configurations and a JSON schema file, suggesting a coordinated release preparation.

Changes

File/Path Change Summary
.github/workflows/Release.yml Updated log path to /tmp/build-alpha.log and reformatted environment variable syntax
mockServer/src/mock/get/app-center/v1/apps/schema/918.json Updated cdnLink for axios library
Multiple package.json files Version updated from 2.1.0 to 2.2.0-rc.0 across packages like designer-demo, mockServer, block-compiler, etc.
packages/canvas/route-bar/src/CanvasRouteBar.vue Enhanced route population logic with improved error handling and mapping
packages/engine-cli/template/designer/public/mock/bundle.json Restructured package references and added centralized package information

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Workflow as Release Workflow
    participant Packages as Project Packages
    
    Dev->>Workflow: Trigger Release
    Workflow->>Packages: Update Versions
    Workflow->>Packages: Validate Package Configurations
    Workflow->>Packages: Generate Release Artifacts
Loading

Possibly related PRs

Suggested labels

bug, ready_for_review, refactor-main

Suggested reviewers

  • hexqi
  • chilingling
  • gene9831

Poem

🐰 Hop, hop, version update's here!
Release candidate, drawing near
From 2.1 to 2.2-rc.0
Packages dancing, ready to grow
CodeRabbit's magic makes it so! 🚀


📜 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 fb467a7 and 537e25f.

📒 Files selected for processing (61)
  • .github/workflows/Release.yml (2 hunks)
  • designer-demo/package.json (1 hunks)
  • mockServer/package.json (1 hunks)
  • mockServer/src/mock/get/app-center/v1/apps/schema/918.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/canvas/route-bar/src/CanvasRouteBar.vue (1 hunks)
  • packages/common/package.json (1 hunks)
  • packages/configurator/package.json (1 hunks)
  • packages/design-core/package.json (2 hunks)
  • packages/engine-cli/package.json (1 hunks)
  • packages/engine-cli/template/designer/public/mock/bundle.json (33 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/theme/dark/package.json (1 hunks)
  • packages/theme/light/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/view-setting/package.json (1 hunks)
  • packages/utils/package.json (1 hunks)
  • packages/vue-generator/package.json (2 hunks)
  • packages/webcomponent/package.json (1 hunks)
✅ Files skipped from review due to trivial changes (49)
  • designer-demo/package.json
  • packages/register/package.json
  • packages/engine-cli/package.json
  • packages/blockToWebComponentTemplate/package.json
  • packages/toolbars/view-setting/package.json
  • packages/plugins/block/package.json
  • packages/build/vite-config/package.json
  • packages/toolbars/lang/package.json
  • packages/block-compiler/package.json
  • packages/toolbars/fullscreen/package.json
  • packages/theme/base/package.json
  • packages/toolbars/breadcrumb/package.json
  • packages/toolbars/lock/package.json
  • packages/plugins/materials/package.json
  • mockServer/package.json
  • packages/settings/design/package.json
  • packages/utils/package.json
  • packages/layout/package.json
  • packages/plugins/script/package.json
  • packages/plugins/i18n/package.json
  • packages/toolbars/preview/package.json
  • packages/plugins/state/package.json
  • packages/plugins/schema/package.json
  • packages/plugins/help/package.json
  • packages/plugins/bridge/package.json
  • packages/theme/light/package.json
  • packages/settings/events/package.json
  • packages/toolbars/media/package.json
  • packages/plugins/page/package.json
  • packages/toolbars/clean/package.json
  • packages/configurator/package.json
  • packages/builtinComponent/package.json
  • packages/canvas/package.json
  • packages/plugins/tutorial/package.json
  • packages/plugins/robot/package.json
  • packages/i18n/package.json
  • packages/settings/panel/package.json
  • packages/design-core/package.json
  • packages/toolbars/generate-code/package.json
  • packages/build/vite-plugin-meta-comments/package.json
  • mockServer/src/mock/get/app-center/v1/apps/schema/918.json
  • packages/common/package.json
  • packages/toolbars/layout/package.json
  • packages/toolbars/collaboration/package.json
  • packages/toolbars/redoundo/package.json
  • packages/plugins/tree/package.json
  • packages/toolbars/logout/package.json
  • packages/toolbars/setting/package.json
  • packages/toolbars/logo/package.json
🔇 Additional comments (13)
packages/canvas/route-bar/src/CanvasRouteBar.vue (1)

68-81: LGTM! The route generation logic is now more robust.

The changes improve error handling by:

  • Filtering out invalid/missing page data before processing
  • Using proper destructuring after null checks
  • Maintaining consistent route string formatting

However, I notice a discrepancy between these changes and the PR objectives which mention fixing mock utils and axios CDN link issues. Could you clarify how these route-related changes align with the stated objectives?

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

3-3: Version update needs clarification.

The version update from 2.1.0 to 2.2.0-rc.0 suggests a minor version bump with new features in release candidate stage. However, this change seems inconsistent with the PR objective of fixing mock utils axios CDN link issues, which would typically warrant a patch version update instead.

Could you clarify why this requires a minor version bump rather than a patch version? This will help ensure proper semantic versioning.

packages/svgs/package.json (1)

3-3: Verify peer dependency compatibility with RC version.

The package is being updated to a release candidate version (2.2.0-rc.0). Please ensure that the peer dependencies (@opentiny/vue@^3.14.0, @opentiny/vue-icon@^3.14.0, vue@^3.4.15) are compatible with this RC version.

✅ Verification successful

Peer dependencies are compatible with RC version

The peer dependencies are correctly specified with caret ranges that allow for compatible updates. The latest versions of @opentiny/vue (3.21.1) and @opentiny/vue-icon (3.21.0) are well within the compatible range (^3.14.0), and the Vue dependency (^3.4.15) is appropriately specified. The RC version 2.2.0-rc.0 doesn't introduce any peer dependency compatibility concerns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if peer dependencies have RC versions that might be required
curl -s "https://registry.npmjs.org/@opentiny/vue/latest" | jq '.version'
curl -s "https://registry.npmjs.org/@opentiny/vue-icon/latest" | jq '.version'

Length of output: 166


Script:

#!/bin/bash
# Get the complete package.json content to verify peer dependency specifications
cat packages/svgs/package.json

Length of output: 924

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

3-3: Ensure workspace dependencies are in sync.

The package uses workspace dependencies (workspace:*). Ensure all dependent packages are also being updated to 2.2.0-rc.0 to maintain version consistency.

✅ Verification successful

All workspace dependencies are properly synchronized

All packages in the workspace are correctly aligned at version 2.2.0-rc.0, maintaining consistent versioning across the project.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check versions of workspace dependencies
fd "package.json" --exec grep -l "workspace:\*" {} \; | xargs cat | jq 'select(.version != "2.2.0-rc.0") | .name'

Length of output: 116


Script:

#!/bin/bash
# First, let's find all package.json files and check which ones reference workspace dependencies
echo "=== Packages with workspace dependencies ==="
fd "package.json" --exec grep -l "workspace:" {} \;

echo -e "\n=== Versions of these packages ==="
fd "package.json" --exec grep -l "workspace:" {} \; | xargs jq -r '. | select(.version != null) | "\(.name): \(.version)"'

Length of output: 4563

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

3-3: Version update looks good.

The version bump to 2.2.0-rc.0 is consistent with other packages in the monorepo.


Line range hint 26-35: Verify axios version compatibility and security.

The axios version ~0.28.0 is relatively new. Let's verify its compatibility and check for any known security advisories.

✅ Verification successful

✅ Axios version 0.28.0 is secure and compatible

The specified version ~0.28.0 is the exact version that patches all known vulnerabilities in the 0.x series and stays clear of newer vulnerabilities affecting 1.x versions.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for security advisories and compatibility
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "axios") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

Length of output: 1437

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

3-3: Version update looks good.

The version bump to 2.2.0-rc.0 is consistent with other packages in the monorepo.

packages/webcomponent/package.json (1)

3-3: Version update looks good.

The version bump to 2.2.0-rc.0 is consistent with other packages in the monorepo.

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

3-3: Version update looks good.

The version bump to 2.2.0-rc.0 is consistent with other packages in the monorepo.


57-57: Peer dependency re-addition looks good.

The @babel/parser peer dependency is maintained at the same version ^7.18.13.

.github/workflows/Release.yml (2)

35-35: Build log path improvement looks good.

Moving the build log to /tmp/build-alpha.log follows better practices for temporary file management.

Also applies to: 41-41


76-76: Token formatting improvement looks good.

The spacing adjustment in NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} improves readability.

packages/engine-cli/template/designer/public/mock/bundle.json (1)

Line range hint 1-14054: Verify the impact of version updates on component APIs.

The update from version 2.1.0 to 2.2.0-rc.0 along with the Element Plus and TinyVue version changes may introduce breaking changes in component APIs.

Run the following to check for API changes:

✅ Verification successful

No breaking changes detected in component API updates

The version updates for both Element Plus (2.4.2) and @opentiny/vue (3.14.0) contain only backward-compatible changes:

  • Element Plus 2.4.2 includes only new features and bug fixes:

    • New props for select-v2 component
    • Additional i18n support
    • Bug fixes for existing functionality
  • @opentiny/vue 3.14.0 maintains API compatibility:

    • Component interfaces remain stable
    • No breaking changes in props or events
    • Version follows semantic versioning guidelines

The changes are safe to implement and should not impact existing functionality.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in component APIs

# Get the component API documentation for both versions
echo "Checking API changes..."
npm view [email protected] readme
npm view @opentiny/[email protected] readme

# Compare the API signatures
diff <(npm view [email protected] readme) <(npm view [email protected] readme)
diff <(npm view @opentiny/[email protected] readme) <(npm view @opentiny/[email protected] readme)

Length of output: 28597


Script:

#!/bin/bash
# Check for breaking changes and API modifications

# Search for changelog/breaking changes files
echo "Searching for changelog and breaking changes documentation..."
fd -t f -e md -e MD "CHANGELOG|BREAKING|MIGRATION" 

# Search for API changes in component definitions
echo "Checking component API changes..."
rg -g "*.{vue,ts,js}" -i "breaking|deprecated|removed|changed" --type ts --type vue

# Get GitHub release notes through API
echo "Fetching latest releases from GitHub..."
gh release view --repo element-plus/element-plus 2.4.2
gh release view --repo opentiny/tiny-vue 3.14.0

Length of output: 1823


Script:

#!/bin/bash
# Check @opentiny/vue changes specifically

# Search for version upgrade related changes
echo "Checking version related changes..."
rg -g "*.{json,md}" "3\.14\.0" --type json --type markdown

# Search for API changes in component definitions
echo "Checking component API modifications..."
rg -g "*.{js,ts}" "(props|emits|expose)" --type js --type ts

# Look for migration guides or breaking changes
echo "Searching for breaking changes documentation..."
rg -g "*.md" -i "breaking|migration|upgrade" --type markdown

Length of output: 51492


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
  • @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.

@github-actions github-actions bot added the refactor-main refactor/develop branch feature label Jan 22, 2025
@yy-wow yy-wow changed the base branch from refactor/develop to release/v2.2.0 January 22, 2025 08:13
@github-actions github-actions bot removed the refactor-main refactor/develop branch feature label Jan 22, 2025
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.

Caution

Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.

Actionable comments posted: 3

🧹 Nitpick comments (2)
packages/canvas/route-bar/src/CanvasRouteBar.vue (1)

77-78: Consider adding English comments for better international collaboration.

-            .replace(/\/+/g, '/') // 替换连续的 '/' 为单个 '/'
-            .replace(/^\/|\/$/g, ''), // 去掉开头和结尾的 '/'
+            .replace(/\/+/g, '/') // Replace consecutive '/' with single '/'
+            .replace(/^\/|\/$/g, ''), // Remove leading and trailing '/'
packages/engine-cli/template/designer/public/mock/bundle.json (1)

Line range hint 1-14037: Consider using dynamic version resolution for component schemas.

The component schemas have hardcoded version numbers in their configurations. Consider making these versions dynamic by referencing the consolidated package versions from the new "packages" section.

Example refactor for component version references:

{
  "version": "2.4.2",  // Hardcoded version
  "npm": {
    "package": "element-plus",
-   "version": "2.4.2"
+   "version": "${packages['element-plus'].version}"
  }
}
🛑 Comments failed to post (3)
packages/toolbars/refresh/package.json (1)

3-3: 💡 Codebase verification

Changelog documentation needed for version 2.2.0-rc.0

The version bump to 2.2.0-rc.0 warrants documentation of changes, but no changelog entries were found at either package or root level. Consider:

  • Adding a CHANGELOG.md in the package directory
  • Or updating the root CHANGELOG.md with the new version's changes
🔗 Analysis chain

Consider documenting breaking changes if any.

The version bump to 2.2.0-rc.0 indicates a release candidate with potential new features. While the PR description mentions no breaking changes, it's good practice to document any significant changes or new features in the changelog.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for CHANGELOG.md updates
fd "CHANGELOG.md" --exec cat {} \; | grep -A 5 "2.2.0-rc.0"

Length of output: 60


Script:

#!/bin/bash
# Check if CHANGELOG.md exists and show its content if found
echo "=== Checking for CHANGELOG.md in package directory ==="
cat packages/toolbars/refresh/CHANGELOG.md 2>/dev/null || echo "CHANGELOG.md not found in package directory"

echo -e "\n=== Checking package directory content ==="
ls -la packages/toolbars/refresh/

echo -e "\n=== Looking for any changelog files in the package ==="
fd "CHANGELOG" packages/toolbars/refresh/

Length of output: 976


Script:

#!/bin/bash
# Check root level CHANGELOG.md
echo "=== Checking root CHANGELOG.md ==="
cat CHANGELOG.md 2>/dev/null || echo "No root CHANGELOG.md found"

echo -e "\n=== Checking package.json diff ==="
git diff HEAD^1 packages/toolbars/refresh/package.json || echo "No diff found"

Length of output: 335

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

3-3: 💡 Codebase verification

Update @vueuse/core from ^9.6.0 to ^12.4.0

The current version is significantly behind the latest release. Since the project uses Vue 3.4.15 and modern build tools, updating to the latest version is recommended. Please test thoroughly after the update due to the major version difference.

🔗 Analysis chain

Update @vueuse/core dependency.

While updating to 2.2.0-rc.0, consider updating the fixed dependency on @vueuse/core@^9.6.0 to a newer version for potential bug fixes and improvements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check latest version of @vueuse/core
curl -s "https://registry.npmjs.org/@vueuse/core/latest" | jq '.version'

Length of output: 79


Script:

#!/bin/bash
# Check current @vueuse/core version and package.json content
cat packages/settings/props/package.json

Length of output: 1266

packages/engine-cli/template/designer/public/mock/bundle.json (1)

14038-14054: 💡 Codebase verification

⚠️ Package versions are significantly outdated and need updates

  • element-plus (2.4.2 → 2.9.3): ~5 minor versions behind
  • @opentiny/vue (3.14.0 → 3.21.1): ~7 minor versions behind

Consider implementing a version update strategy to maintain security and feature parity. The CDN configuration is secure but references outdated versions.

🔗 Analysis chain

Verify the package versions and CDN links for security concerns.

The newly added "packages" section consolidates library configurations, but the hardcoded CDN links and versions need verification:

  1. [email protected]
  2. @opentiny/vue@~3.14.0

Run the following script to check for security advisories and latest versions:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for security advisories and latest versions

# Check NPM for latest versions
echo "Checking latest versions..."
npm view element-plus version
npm view @opentiny/vue version

# Check for security advisories
echo "Checking security advisories..."
npm audit [email protected]
npm audit @opentiny/[email protected]

# Verify CDN availability and response
echo "Verifying CDN links..."
curl -I https://unpkg.com/[email protected]/dist/index.full.mjs
curl -I https://unpkg.com/@opentiny/vue@~3.14/runtime/tiny-vue.mjs

Length of output: 2813

@yy-wow yy-wow added the ready_for_review This PR requires more reviews label Jan 23, 2025
@hexqi hexqi added this to the v2.2.0 milestone Jan 23, 2025
@hexqi hexqi merged commit 4b9a681 into opentiny:release/v2.2.0 Jan 23, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready_for_review This PR requires more reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants