Skip to content

chore: update and rename main.yaml to release.yaml #129

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 19, 2025
Merged

chore: update and rename main.yaml to release.yaml #129

merged 1 commit into from
Aug 19, 2025

Conversation

shenxianpeng
Copy link
Contributor

@shenxianpeng shenxianpeng commented Aug 19, 2025 •
edited by coderabbitai bot
Loading

Right now, if we published a pre-release, the tag v1 will also be updated to point to the pre-release.

which is not what we wanted. We should change the type to released

Summary by CodeRabbit

  • Chores
    • Renamed the release workflow to “Release” for clearer identification in pipelines.
    • Adjusted the release trigger to run on “released” events instead of “published,” aligning with platform semantics and improving reliability of automated releases.
    • No changes to product functionality; distribution cadence and user experience remain unaffected.

@shenxianpeng shenxianpeng added the enhancement New feature or request label Aug 19, 2025
@shenxianpeng shenxianpeng requested a review from a team as a code owner August 19, 2025 19:05
@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Aug 19, 2025 •
edited
Loading

Caution

Review failed

The pull request is closed.

Walkthrough

Renamed the GitHub Actions workflow from “Main” to “Release” and updated its trigger to run on release events with type “released” instead of “published”. No other workflow steps or logic changed.

Changes

Cohort / File(s) Summary of Changes
GitHub Actions workflow
/.github/workflows/release.yaml		 Workflow name updated to “Release”. Trigger adjusted: on.release.types changed from [published] to [released]. No other modifications.

Sequence Diagram(s)

sequenceDiagram
    actor Dev as Maintainer
    participant GH as GitHub Releases
    participant WF as Workflow: Release

    Dev->>GH: Create/finish a Release (action: released)
    GH-->>WF: Trigger on release[type=released]
    rect rgba(200,240,255,0.3)
    note right of WF: Workflow jobs execute (unchanged steps)
    end
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers—new tags in the breeze,
“Release,” I thump, as the pipeline agrees.
From published to released, a subtle hop,
Carrot-shaped badges rise to the top.
I nibble logs, all greens at ease—
Another swift launch through automated trees.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

📜 Recent review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 77cf05a and ab16be8.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch shenxianpeng-patch-1

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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
Copy link
Contributor

Commit-Check ❌

Commit rejected by Commit-Check.                                  
                                                                  
  (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)  
   / ._. \      / ._. \      / ._. \      / ._. \      / ._. \   
 __\( C )/__  __\( H )/__  __\( E )/__  __\( C )/__  __\( K )/__ 
(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)
   || E ||      || R ||      || R ||      || O ||      || R ||   
 _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._ 
(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)
 `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´ 
                                                                  
Commit rejected.                                                  
                                                                  
Type message check failed => Update and rename main.yaml to release.yaml

 
It doesn't match regex: ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)|(Merge).*|(fixup!.*)
The commit message should be structured as follows:

 <type>[optional scope]: <description>
 [optional body]
 [optional footer(s)]

 More details please refer to https://www.conventionalcommits.org
Suggest: please check your commit message whether matches above regex

@shenxianpeng shenxianpeng changed the title Update and rename main.yaml to release.yaml chore: update and rename main.yaml to release.yaml Aug 19, 2025
@shenxianpeng shenxianpeng enabled auto-merge (squash) August 19, 2025 19:07
@shenxianpeng shenxianpeng disabled auto-merge August 19, 2025 19:07
@shenxianpeng shenxianpeng merged commit ea1ae5c into main Aug 19, 2025
3 of 4 checks passed
@shenxianpeng shenxianpeng deleted the shenxianpeng-patch-1 branch August 19, 2025 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@shenxianpeng