Skip to content

[ci] Fix matching tag for release branch - #805

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release-tag-matching
Apr 14, 2025
Merged

[ci] Fix matching tag for release branch#805
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release-tag-matching

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented Apr 11, 2025 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil kvapss@gmail.com

Summary by CodeRabbit

  • Chores
    • Updated the automated release process to format version tags with a "v" prefix for consistent version naming.
    • Performed minor cleanup to improve overall code clarity.

@kvaps
[ci] Fix matching tag for release branch
6d2ea12 
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai

coderabbitai Bot commented Apr 11, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Walkthrough

This pull request modifies the GitHub Actions workflow responsible for extracting a version tag from the branch name. The extraction logic now prefixes the version number with a "v" (e.g., transforming "1.2.3" to "v1.2.3") by replacing the assignment from match[1] to v${match[1]}. Additionally, a blank line was removed to clean up the code formatting, while the overall control flow and error handling remain unchanged.

Changes

File(s) Changes Summary
.github/workflows/pull-requests-release.yaml Updated tag extraction logic: now assigns v${match[1]} instead of match[1]; removed an extraneous blank line for improved code formatting.

Sequence Diagram(s)

sequenceDiagram
    participant Action as GitHub Action
    participant Parser as Version Parser
    participant Output as Workflow Output

    Action->>Parser: Extract branch name version with regex
    Parser-->>Action: Return version (e.g., "1.2.3")
    Action->>Output: Prefix with "v" to form "v1.2.3"
Loading

Poem

I'm a bunny and I hop with glee,
A "v" now leads our version spree.
Branch names parsed with care so neat,
Code is tidy, oh what a treat!
Happy hops in lines we meet.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
📜 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 d7914ff and 6d2ea12.

📒 Files selected for processing (1)
  • .github/workflows/pull-requests-release.yaml (1 hunks)
🔇 Additional comments (1)
.github/workflows/pull-requests-release.yaml (1)

53-61: Tag Extraction Update: Ensuring "v" Prefix

The updated logic now correctly prefixes the extracted version number with a "v" (i.e. converting match[1] to v${match[1]}), which aligns with our release versioning conventions. Please verify that any downstream steps or documentation referencing the tag format are adjusted accordingly.

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.
    • 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@kvaps
Andrei Kvapil (kvaps) merged commit d8f3f2d into main Apr 14, 2025
@kvaps
Andrei Kvapil (kvaps) deleted the release-tag-matching branch April 14, 2025 07:04
@coderabbitai coderabbitai Bot mentioned this pull request Apr 16, 2025
Merged
Andrei Kvapil (kvaps) added a commit that referenced this pull request Apr 17, 2025
@kvaps
[ci] Fix matching tag for release branch (#805)
7ca8ff0 
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated the automated release process to format version tags with a
"v" prefix for consistent version naming.
  - Performed minor cleanup to improve overall code clarity.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
This was referenced Apr 24, 2025
Merged
Merged
Merged
This was referenced May 22, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lllamnyp Timofei Larkin (lllamnyp) Awaiting requested review from lllamnyp lllamnyp is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@kvaps