test: cover modern services winning over same-named v2 tools on install - #7575
Conversation
Also fix the install container JSDoc and keep the prepare test from leaving a ruby prepared marker behind. Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: containerbase/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe install-tool comment now documents generic v2 shell-tool bindings and modern-service precedence. Tests verify Ruby installation dispatch when a same-named v2 tool exists and stub preparation state handling. ChangesRuby installer precedence
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to This change clarifies installer precedence and adds isolated test coverage. The reported v2 pip-mirror behavior was not introduced here, so no actionable merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Changes
Follow-up to the python and ruby conversion (#7558, #7559):
install-tooluses the TypeScript service when a custom image ships a v2 shell tool with the same name, like the existing prepare test.Release note for #7558: v2 shell tools no longer get
PIP_INDEX_URLfromURL_REPLACE_*. A custom v2 tool that runspip installbehind a pypi mirror replacement has to set the index itself.Context
AI assistance disclosure
Did you use AI tools to create any part of this pull request?
Code and tests were written by Claude Opus 5.5 in Claude Code.
Use of AI in replying to PR comments
Who answers review comments:
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
🤖 Generated with Claude Code
Summary by CodeRabbit