fix(automation): restore pinned OpenCode bootstrap - #200
Conversation
|
Warning Review limit reached
Next review available in: 21 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesOpenCode 설치 경계
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/commercial-development-agent/src/opencode-install-contract.test.mjs`:
- Around line 12-15: Update the opencode-ai version assertion in the test to
require the reviewed exact version by replacing the broad semantic-version regex
check with an exact `1.18.9` expectation.
- Around line 16-18: Update the test around the workspace configuration
assertion to parse the YAML content and compare the parsed onlyBuiltDependencies
value exactly against ['opencode-ai']. Replace the substring-based check in the
relevant test with a structured equality assertion so additional entries such as
another-package cause the test to fail.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 749fc203-9f56-455f-8bee-300e4332cfe8
📒 Files selected for processing (2)
packages/commercial-development-agent/src/opencode-install-contract.test.mjspnpm-workspace.yaml
RCA
The hourly OpenCode commercial-development workflow fails before any repository selection or model work.
pnpm@10.15.0installs the exactopencode-ai@1.18.9dependency but blocks dependency lifecycle scripts by default; the subsequentopencode --versionboundary therefore fails because the package postinstall never materialized its platform executable.Remedy
opencode-aiin the pnpm workspace build allowlist;1.18.9package pin and all model/governance boundaries unchanged;esbuildlifecycle script because this failure does not require it.The first commit captures the failing contract before the configuration remedy. The final contract is intentionally scoped to the first failing boundary; receipt generation after an earlier bootstrap failure is a separate diagnostics hardening concern, not required to restore the executable.
Acceptance
Verify the exact OpenCode installationon a fresh run.Summary by CodeRabbit
개선 사항
테스트