ci: remove unnecessary git_tag option

[taj54]

• Simplified version bump workflow.
• Removed redundant git_tag setting.
• Improved workflow efficiency.

Summary by CodeRabbit

• Chores
  • Updated release workflow to rely on default tagging behavior during version bumps.
  • This may enable automatic version tags in the release process.
  • No changes to application functionality or user experience.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Removed the explicit git_tag: false parameter from the Universal Version Bump step in .github/workflows/version-bump.yml, allowing the action to use its default tagging behavior. No other workflow configuration was changed.

Changes

Cohort / File(s)	Summary of Changes
CI workflow: Version bump \.github/workflows/version-bump.yml	Removed git_tag: false from the Universal Version Bump step; tagging behavior now follows the action’s default. All other settings unchanged.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor Dev as Developer
    participant GH as GitHub Actions
    participant UVB as Universal Version Bump Action
    participant Repo as Repo

    Dev->>GH: Push/PR triggers workflow
    GH->>UVB: Run version-bump job
    UVB->>Repo: Compute next version
    alt Default tagging behavior
        UVB->>Repo: Create git tag (per action default)
    else If action default skips tagging
        UVB-->Repo: No tag created
    end
    UVB->>GH: Output version and status

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(deps): update universal-version-bump to v0.12.0 #29 — Also modifies the Universal Version Bump step in the same workflow by updating the action version.
• feat(workflow): simplify version bump process #25 — Adjusts the same step’s git_tag setting (adds git_tag: false), directly related to this removal.

Poem

A bump in the night, a tag in the day,
I twitch my ears—defaults lead the way.
No extra flags, just clean and spry,
The version hops, oh my, oh my!
With gentle paws I stamp “OK”—
Ship it swift; we’re on our way. 🐇✨

---

📜 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 314d738 and 66ea689.

📒 Files selected for processing (1)

• .github/workflows/version-bump.yml (0 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• 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>, 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 or @coderabbit 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.