Skip to content

chore:Adds 'v' to version tag#93

Merged
agustingroh merged 1 commit into
mainfrom
chore/change-semver-format-for-tagging
Aug 22, 2025
Merged

chore:Adds 'v' to version tag#93
agustingroh merged 1 commit into
mainfrom
chore/change-semver-format-for-tagging

Conversation

@agustingroh

@agustingroh agustingroh commented Aug 22, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Standardized release tags to include a “v” prefix (e.g., v1.2.3) for consistency with common versioning conventions and clearer release identifiers.
    • Improves compatibility with tools and integrations that expect v-prefixed tags, making releases easier to discover.
    • If you reference tag names in scripts or integrations, update them to the new format.
    • No functional changes to the app.

@agustingroh agustingroh requested a review from Alex-1089 August 22, 2025 14:59
@agustingroh agustingroh self-assigned this Aug 22, 2025
@agustingroh agustingroh added the enhancement New feature or request label Aug 22, 2025
@coderabbitai

coderabbitai Bot commented Aug 22, 2025

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

Walkthrough

The workflow .github/workflows/version-tag.yml updates the Apply Tag step to prefix Git tags with "v", changing git tag "${{ env.package_app_version }}" to git tag "v${{ env.package_app_version }}". No other steps or files are modified.

Changes

Cohort / File(s) Summary of Changes
CI/CD Workflow: Version Tagging
\.github/workflows/version-tag.yml
Updated tag creation command to prefix tags with "v": git tag "v${{ env.package_app_version }}" instead of git tag "${{ env.package_app_version }}".

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant GH as GitHub Actions
    participant Repo as Git Repository

    rect rgb(235, 245, 255)
    note over GH: Workflow runs (e.g., on release/publish)
    GH->>Repo: Checkout code
    GH->>GH: Determine env.package_app_version
    end

    rect rgb(245, 255, 235)
    note over GH,Repo: Apply Tag (changed behavior)
    GH->>Repo: git tag "v${{ env.package_app_version }}"
    GH->>Repo: git push origin --tags
    end
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at version cheer,
A little “v” now fronts the year.
Hop-tag, push-tag—clean and spry,
Releases labeled, carrots high.
In verdant logs, the truth I see:
A tidy trail of v for me. 🥕✨

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 1ef7762 and 6894b2c.

📒 Files selected for processing (1)
  • .github/workflows/version-tag.yml (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/change-semver-format-for-tagging

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

Copy link
Copy Markdown

SCANOSS SCAN Completed 🚀

  • Detected components: 5
  • Undeclared components: 5
  • Declared components: 0
  • Detected files: 31
  • Detected files undeclared: 31
  • Detected files declared: 0
  • Licenses detected: 2
  • Licenses detected with copyleft: 0
  • Policies: ✅ 1 pass (1 total)

View more details on SCANOSS Action Summary

@agustingroh agustingroh merged commit b2b418d into main Aug 22, 2025
6 of 7 checks passed
@agustingroh agustingroh deleted the chore/change-semver-format-for-tagging branch August 22, 2025 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants