Update tag-name variable in cli-release.yml for correct versioning in brew

[egorikftp]

No description provided.

[coderabbitai]

Walkthrough

This pull request modifies the .github/workflows/cli-release.yml file to update the Homebrew formula action's input parameter. The change replaces RELEASE_TAG with VERSION_NAME as the value for the tag-name field. The download URL configuration continues to reference both RELEASE_TAG and VERSION_NAME variables, with only the tag-name parameter being altered in the action invocation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Single file modified (GitHub Actions workflow configuration)
• Localized parameter update with no logic changes
• Verify that VERSION_NAME is the correct and intended parameter for Homebrew formula tagging
• Confirm the semantic difference between RELEASE_TAG and VERSION_NAME is appropriate for this use case

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, making it impossible to assess relevance to the changeset.	Add a description explaining why the tag-name variable was changed from RELEASE_TAG to VERSION_NAME and the impact on Homebrew formula updates.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the tag-name variable in cli-release.yml for Homebrew versioning.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch task/cli-brew-tap

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/cli-release.yml (1)

26-47: Consider adding inline comment for maintainability.

The distinction between RELEASE_TAG ("cli-$VERSION_NAME") used for GitHub release tags and VERSION_NAME used for the Homebrew formula version is important context. Consider adding a brief comment in the "Prepare release information" step to explain this separation for future maintainers.

      - name: Prepare release information
        run: |
          VERSION_NAME=$(grep "^cli-version" gradle/cli.versions.toml | cut -d '"' -f 2)
+         # RELEASE_TAG includes the "cli-" prefix for GitHub releases; VERSION_NAME is clean for Homebrew
          RELEASE_TAG="cli-$VERSION_NAME"

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 86a8c36 and fee6920.

📒 Files selected for processing (1)

• .github/workflows/cli-release.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (ubuntu-latest)