fix: refresh version cache after setup.sh completes

[marcusquinn]

Summary

• setup.sh deploys the VERSION file to ~/.aidevops/agents/VERSION but never refreshes the session greeting cache (~/.aidevops/cache/session-greeting.txt)
• This causes stale version reporting when running setup.sh directly (e.g. after a manual git pull) without going through aidevops update
• Fix: run aidevops-update-check.sh at the end of setup to sync the cached version

Testing

1. Run ./setup.sh directly (not via aidevops update)
2. Check ~/.aidevops/cache/session-greeting.txt shows correct version
3. New AI sessions should report the correct version immediately

Summary by CodeRabbit

• Chores
  • Added automatic version and cache refresh during the setup process to ensure the installation reflects the current state. This executes silently as part of the standard setup flow.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Walkthrough

The change adds version cache refresh logic to setup.sh by invoking aidevops-update-check.sh at two strategic points: after disabling on-demand MCPs and before final usage output, both conditionally executing only if the helper script exists.

Changes

Cohort / File(s)	Summary
Version Cache Refresh setup.sh	Introduces two identical post-setup blocks that silently invoke aidevops-update-check.sh (if executable) to refresh cached version data during setup completion.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• fix: update check + add /log-issue-aidevops command #248: Modifies aidevops-update-check.sh's version-file lookup behavior, directly intersecting with this PR's new invocations of that script.
• feat: add tool update checking to setup.sh and aidevops CLI #56: Adds the aidevops-update-check.sh script and integrates tool-update checks into setup workflows—foundational to this PR's post-setup cache refresh pattern.

Poem

🔄 Setup spins twice with whispered grace,
Cache refreshed in its rightful place,
Version echoes through the DevOps night,
Two gentle calls, both clean and tight. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: refreshing the version cache after setup.sh completes, which directly addresses the PR's core objective.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/setup-version-sync

---

No actionable comments were generated in the recent review. 🎉

---

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, 33 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Sun Feb 8 02:50:59 UTC 2026: Code review monitoring started
Sun Feb 8 02:50:59 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 33

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 33
• VULNERABILITIES: 0

Generated on: Sun Feb 8 02:51:02 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