Skip to content

Conversation

@zzcr
Copy link
Member

@zzcr zzcr commented Jan 13, 2025

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)

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 new GitHub Actions workflows for:
      • Renderless Theme Runtime publishing
      • UI component publishing
  • Bug Fixes
    • Corrected a typo in version validation in an existing workflow
  • Chores
    • Enhanced CI/CD infrastructure for component and package releases
    • Implemented manual dispatch workflows with component-specific build and publish capabilities

@coderabbitai
Copy link

coderabbitai bot commented Jan 13, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces modifications to GitHub Actions workflows, focusing on publishing and release processes. The changes include a typo correction in an existing workflow file and the addition of two new workflow files for dispatching UI and renderless theme runtime builds. These workflows enable manual triggering of component builds and releases with specific input parameters, concurrency controls, and standardized build and publish steps.

Changes

File Change Summary
.github/workflows/dispatch-all-publish-alpha.yml Corrected a typo from vserion to version in version validation step
.github/workflows/dispatch-renderless-theme-publish-alpha.yml New workflow for manually dispatching renderless theme runtime builds with component-specific build and publish steps
.github/workflows/dispatch-ui-publish-alpha.yml New workflow for manually dispatching UI component builds with branch naming validation and publish process

Possibly related PRs

Suggested labels

ci

Suggested reviewers

  • kagol

Poem

🐰 Workflows dance, a CI delight,
Typos fixed with rabbit's might,
Components build, releases soar,
GitHub Actions open a new door!
Publish and build, with scripts so neat,
Our rabbit's workflow can't be beat! 🚀


📜 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 187cc8e and 48da23b.

📒 Files selected for processing (3)
  • .github/workflows/dispatch-all-publish-alpha.yml (1 hunks)
  • .github/workflows/dispatch-renderless-theme-publish-alpha.yml (1 hunks)
  • .github/workflows/dispatch-ui-publish-alpha.yml (1 hunks)

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.

@petercat-assistant
Copy link

Walkthrough

This pull request introduces new GitHub Actions workflows for publishing alpha versions of UI and renderless components. It includes the addition of two new workflow files and modifications to an existing one to support these publishing actions.

Changes

File Summary
.github/workflows/dispatch-all-publish-alpha.yml Minor modification to existing workflow for alpha publishing.
.github/workflows/dispatch-renderless-theme-publish-alpha.yml New workflow added for renderless theme alpha publishing.
.github/workflows/dispatch-ui-publish-alpha.yml New workflow added for UI alpha publishing.

@zzcr zzcr merged commit aecb949 into dev Jan 13, 2025
5 checks passed
components:
description: |
输入需要打包的模块名称,多个以英文逗号分隔,
例如: `theme,renderless,runtime`

Choose a reason for hiding this comment

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

Verify that the secrets and tokens used in this workflow are correctly configured in the repository settings to prevent unauthorized access or failures during the workflow execution.

type: string
concurrency:
group: ${{ github.workflow }}-${{ github.sha }}
cancel-in-progress: true

Choose a reason for hiding this comment

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

Check that all necessary permissions are granted to this workflow to interact with other GitHub services or external APIs, ensuring smooth execution without permission-related errors.

@github-actions
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

@kagol kagol deleted the fix-alpha-all-publish-0113 branch April 14, 2025 12:20
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.

2 participants