Fixed docs release GHA to retain installer.

[AlexSkrypnyk]

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow to allow manual triggering with customizable installer version.
  • Enhanced PHAR installer testing to include additional command options.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The GitHub Actions workflow for releasing and testing the PHAR installer now supports manual triggering with an optional installer_version input to override the version used. The "Add version" step uses this input if provided, otherwise derives the version from the GitHub ref as before. The "Test PHAR" step was updated to add the --no-cleanup flag alongside --no-interaction.

Changes

File(s)	Change Summary
.github/workflows/vortex-release-docs.yml	Added workflow_dispatch with optional installer_version input; updated "Add version" step to use input if given; added --no-cleanup flag to PHAR test command

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• [#1663] Added removal of installer after installation success. #1826: Introduced the --no-cleanup flag and its handling in the PHAR installer command and tests, directly related to the workflow update in this PR.

Poem

🐇
Now workflows listen when we call,
With versions set, or none at all.
Tests run with flags that keep things near,
No cleanup means the logs appear.
A hop, a skip, a version clear!
🎉🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 62f00f0 and df7b8f3.

📒 Files selected for processing (1)

• .github/workflows/vortex-release-docs.yml (2 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/release-docs-25.7.0

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (bbee5c4) to head (62f00f0).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #1852       +/-   ##
===========================================
- Coverage    82.68%   0.00%   -82.69%     
===========================================
  Files           39       1       -38     
  Lines         1640      10     -1630     
===========================================
- Hits          1356       0     -1356     
+ Misses         284      10      -274     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.