4958: address full-loop auto-release review feedback

[marcusquinn]

Summary

• update the auto-release snippet to run version-manager.sh from the canonical repo directory to avoid worktree-local version bumps
• align release commit message with tag format by using the v prefix in NEW_VERSION
• make local deployment explicitly non-interactive and keep failures non-blocking without suppressing output

Verification

• markdown-formatter check .agents/scripts/commands/full-loop.md

Closes #4958

Summary by CodeRabbit

• Chores
  • Improved version bump execution context during releases.
  • Updated deployment setup invocation to use non-interactive mode.
  • Enhanced commit message formatting for version tags.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the automated release process by addressing several feedback points. It ensures that version management operations are performed correctly within the main repository, standardizes release commit messages for consistency, and improves the local deployment experience by making it non-interactive while allowing output to be visible.

Highlights

• Version Management: The version-manager.sh script now executes from the canonical repository directory, preventing unintended version bumps in worktree-local environments.
• Release Commit Formatting: The release commit message now consistently includes a 'v' prefix for the NEW_VERSION to align with the tag format.
• Local Deployment: Local deployment via setup.sh is now explicitly non-interactive and continues to be non-blocking, but output suppression has been removed for better visibility.

Changelog

• .agents/scripts/commands/full-loop.md
  • Modified the execution context for version-manager.sh to ensure it runs from the $CANONICAL_DIR.
  • Prepended "v" to the NEW_VERSION in the release commit message.
  • Added the --non-interactive flag to the setup.sh command and removed 2>/dev/null.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ffec5083-b797-4df3-9c93-b7efcaa1b2d6

📥 Commits

Reviewing files that changed from the base of the PR and between 9502583 and c0b6a49.

📒 Files selected for processing (1)

• .agents/scripts/commands/full-loop.md

---

Walkthrough

Three targeted corrections to the release automation script address critical review feedback: version-manager.sh execution context, version tag prefix consistency, and explicit non-interactive deployment mode.

Changes

Cohort / File(s)	Summary
Release Script Adjustments .agents/scripts/commands/full-loop.md	Three corrections applied: (1) version-manager.sh now executes within a subshell with directory change to $CANONICAL_DIR to ensure version modifications occur in the canonical repository; (2) commit message updated with v prefix for consistency with git tags; (3) setup.sh invocation changed to use explicit --non-interactive flag instead of error suppression via 2>/dev/null.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🔄 Three fixes, precision flows,
Version tags with prefix glow,
Subshells shift, directories align,
DevOps debt removed by design—
Quality maintained, excellence shows! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '4958: address full-loop auto-release review feedback' directly references the linked issue and accurately summarizes the main purpose: addressing review feedback on the full-loop auto-release script.
Linked Issues check	✅ Passed	The PR successfully implements all three requirements from issue #4958: running version-manager.sh from canonical directory, adding v prefix to version in commit message, and making setup.sh non-interactive while preserving error visibility.
Out of Scope Changes check	✅ Passed	All changes are narrowly scoped to the full-loop.md file and directly address the three critical/high/medium review findings identified in issue #4958; no extraneous modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/issue-4958-quality-debt

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

[github-actions]

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 364 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Sun Mar 15 23:27:09 UTC 2026: Code review monitoring started
Sun Mar 15 23:27:09 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 364

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 364
• VULNERABILITIES: 0

Generated on: Sun Mar 15 23:27:12 UTC 2026

---

Generated by AI DevOps Framework Code Review Monitoring

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

The pull request modifies the full-loop.md script to ensure the version-manager.sh script is executed from the correct directory, adds a 'v' prefix to the version number in the release commit message for consistency, and updates the local deployment step to use a --non-interactive flag for setup.sh instead of redirecting stderr, indicating improved script automation.