ci: update release triggers

[MSevey]

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Refactor
  • Improved the release workflow to trigger on tag pushes and manual dispatch for more flexible release management.

[coderabbitai]

Walkthrough

The CI release workflow has been updated to be more flexible, now triggering on any tag push rather than just specific version patterns. Additionally, the job conditions have been expanded to run on tag events, ensuring that the release process can also be manually triggered if necessary.

Changes

File Path	Change Summary
.github/workflows/.../ci_release.yml	Updated tag trigger to wildcard; added tag push to release job conditions.

Poem

In the realm of code, where actions flow,
A rabbit tweaked the CI's glow.
Now any tag can start the dance,
Release the code, give change a chance! 🚀🐰

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 0795eba and 4eb2862.

Files selected for processing (1)

• .github/workflows/ci_release.yml (2 hunks)

Additional comments: 2

.github/workflows/ci_release.yml (2)

• 8-8: The tag trigger pattern has been updated to a wildcard pattern "v*". This change aligns with the PR objectives to trigger CI processes for a broader range of tag names.

• 40-42: The conditional check for the release job has been correctly updated to include both workflow_dispatch and tag pushes that match the pattern 'refs/tags/v'. This ensures that the release job is triggered automatically when a new tag is pushed, which is in line with the PR objectives.

[nashqueue]

utAck