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

ci(workflows): added automatic upgrade function for external test packages #2804

Merged
merged 4 commits into from
Jan 15, 2025

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented Jan 14, 2025

PR

添加外部测试包自动升级patch版本号功能

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)

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:

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

  • New Features

    • Added an optional -u flag to the release:alpha command.
    • Introduced ability to automatically upgrade package patch version during release.
  • Workflow Changes

    • Removed branch name validation checks in GitHub workflows.
    • Modified release process command parameters.
  • Improvements

    • Enhanced version management functionality in the release process.
    • Provided more flexible version control for package releases.

Copy link

coderabbitai bot commented Jan 14, 2025

Walkthrough

This pull request introduces modifications to the release workflow and CLI for alpha releases. The changes remove branch name validation checks in GitHub Actions workflows for renderless theme and UI publishing. Additionally, the CLI's release alpha command now supports an optional -u flag to automatically update package versions. The modifications aim to provide more flexibility in the release process by eliminating strict branch name constraints and enabling automatic patch version incrementation.

Changes

File Change Summary
.github/workflows/dispatch-renderless-theme-publish-alpha.yml Removed branch name validation check, updated release command to pnpm release:alpha -u
.github/workflows/dispatch-ui-publish-alpha.yml Deleted "Parse Components" job step, modified release command to pnpm release:alpha -u
internals/cli/src/commands/release/releaseAlpha.ts Added getPatchVersion function, updated releaseAlpha to support version update, added updateVersion parameter
internals/cli/src/index.ts Added -u, --updateVersion option to release:alpha command

Sequence Diagram

sequenceDiagram
    participant CLI
    participant ReleaseProcess
    participant NPM
    participant Packages

    CLI->>ReleaseProcess: Execute release:alpha
    alt With -u flag
        ReleaseProcess->>NPM: Check current package versions
        NPM-->>ReleaseProcess: Return current versions
        ReleaseProcess->>Packages: Update patch versions
    else Without -u flag
        ReleaseProcess->>Packages: Proceed without version changes
    end
    ReleaseProcess->>CLI: Complete release process
Loading

Possibly related PRs

Suggested labels

enhancement, chore

Suggested reviewers

  • kagol

Poem

🐰 Hopping through code with glee,
Release workflows now set free!
No branch constraints to bind,
Versions update, so refined!
Alpha releases dance and play,
CodeRabbit's magic saves the day! 🚀

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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.

Copy link

Walkthrough

This PR introduces an automatic upgrade function for external test packages in the CI workflows. It modifies the release process to include an option for automatically upgrading the patch version of packages. The changes involve updates to workflow files and the release script to support this new functionality.

Changes

Files Summary
.github/workflows/dispatch-renderless-theme-publish-alpha.yml, .github/workflows/dispatch-ui-publish-alpha.yml Minor updates to the workflow files to support automatic version upgrades.
internals/cli/src/commands/release/releaseAlpha.ts Introduces a function to automatically upgrade the patch version of packages and modifies the release process to include this functionality.
internals/cli/src/index.ts Updates the CLI command to include an option for automatic patch version upgrades.

Copy link

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

Copy link

@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: 2

🧹 Nitpick comments (2)
internals/cli/src/commands/release/releaseAlpha.ts (1)

50-54: Add type safety to releaseAlpha function.

The function should use proper TypeScript types for its parameters.

Apply this improvement:

-export const releaseAlpha = ({ updateVersion }) => {
+interface ReleaseAlphaOptions {
+  updateVersion: boolean;
+}
+
+export const releaseAlpha = ({ updateVersion }: ReleaseAlphaOptions) => {
   const distLists = ['dist3/', 'dist2/', 'renderless/dist', 'theme/dist', 'theme-mobile/dist', 'theme-saas/dist']
   distLists.forEach((item) => {
-    findAllpage(pathFromPackages(item), updateVersion)
+    findAllPages(pathFromPackages(item), { updateVersion })
   })
 }
internals/cli/src/index.ts (1)

12-16: Consider adding English descriptions for better internationalization.

The command descriptions are currently in Chinese, which might be difficult for non-Chinese speaking contributors to understand.

Consider updating the descriptions:

 program
   .command('release:alpha')
-  .description('转换为组织名为@opentinyvue的包')
+  .description('Convert packages to @opentinyvue organization')
   .option('-u, --updateVersion', '是否自动升级patch版本号', false)
   .action(releaseAlpha)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8f1b566 and 3124f87.

📒 Files selected for processing (4)
  • .github/workflows/dispatch-renderless-theme-publish-alpha.yml (1 hunks)
  • .github/workflows/dispatch-ui-publish-alpha.yml (1 hunks)
  • internals/cli/src/commands/release/releaseAlpha.ts (1 hunks)
  • internals/cli/src/index.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR Unit Test
🔇 Additional comments (2)
.github/workflows/dispatch-ui-publish-alpha.yml (1)

55-55: LGTM!

The addition of the -u flag aligns with the CLI changes to enable automatic version updates.

.github/workflows/dispatch-renderless-theme-publish-alpha.yml (1)

84-84: LGTM!

The addition of the -u flag aligns with the CLI changes to enable automatic version updates.

internals/cli/src/commands/release/releaseAlpha.ts Outdated Show resolved Hide resolved
Copy link

@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: 2

🧹 Nitpick comments (2)
internals/cli/src/commands/release/releaseAlpha.ts (1)

50-54: Add TypeScript type definitions.

The function parameters should have proper TypeScript type definitions for better type safety.

-export const releaseAlpha = ({ updateVersion }) => {
+interface ReleaseAlphaOptions {
+  updateVersion?: boolean;
+}
+
+export const releaseAlpha = ({ updateVersion }: ReleaseAlphaOptions) => {
   const distLists = ['dist3/', 'dist2/', 'renderless/dist', 'theme/dist', 'theme-mobile/dist', 'theme-saas/dist']
   distLists.forEach((item) => {
-    findAllpage(pathFromPackages(item), updateVersion)
+    findAllPages(pathFromPackages(item), updateVersion)
   })
 }
internals/cli/src/index.ts (1)

12-16: Consider adding English translations for option descriptions.

For better international developer experience, consider providing English translations for the command and option descriptions.

 program
   .command('release:alpha')
-  .description('转换为组织名为@opentinyvue的包')
+  .description('Convert packages to @opentinyvue organization')
   .option('-u, --updateVersion', '是否自动升级patch版本号', false)
+  .option('-u, --updateVersion', 'Automatically upgrade patch version number', false)
   .action(releaseAlpha)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8f1b566 and 1ed91e2.

📒 Files selected for processing (4)
  • .github/workflows/dispatch-renderless-theme-publish-alpha.yml (1 hunks)
  • .github/workflows/dispatch-ui-publish-alpha.yml (1 hunks)
  • internals/cli/src/commands/release/releaseAlpha.ts (1 hunks)
  • internals/cli/src/index.ts (1 hunks)
🔇 Additional comments (2)
.github/workflows/dispatch-ui-publish-alpha.yml (1)

55-55: Verify the implications of removing branch name validation.

The removal of branch name validation could potentially allow releases from unintended branches. Please ensure this aligns with the project's release strategy.

✅ Verification successful

Branch validation removal is acceptable in this context.

The workflow's security is maintained through:

  • Manual trigger requirement (workflow_dispatch)
  • Required component selection input
  • NPM token protection for publishing
  • Explicit checkout reference using github.ref_name
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check current branch patterns used in alpha releases
git branch -r | grep -E 'alpha|release'

Length of output: 41


Script:

#!/bin/bash
# Check the current workflow file
echo "=== Current workflow file ==="
cat .github/workflows/dispatch-ui-publish-alpha.yml

echo -e "\n=== Related workflow files ==="
fd "workflow" .github/workflows --type f --exec cat {}

echo -e "\n=== Package.json release scripts ==="
fd "package.json" --type f --exec sh -c 'echo "=== $1 ==="; cat "$1" | jq -r ".scripts | select(. != null)"' sh {}

Length of output: 46409

.github/workflows/dispatch-renderless-theme-publish-alpha.yml (1)

84-84: Changes are consistent with UI workflow.

The modifications align with the changes made in the UI publish workflow, maintaining consistency across the release processes.

@zzcr zzcr merged commit 6d8081a into dev Jan 15, 2025
11 of 12 checks passed
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