fix: pin managed hooks to installed CLI - #332
Conversation
|
Warning Review limit reachedNext included review available in 1 minute. View limit detailsLimit details: You’ve used the included review currently available. This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Comment |
There was a problem hiding this comment.
All reported issues were addressed across 2 files
Shadow auto-approve: would not auto-approve because issues were found.
Re-trigger cubic
|
There was a problem hiding this comment.
0 issues found across 1 file (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would auto-approve. Bug fix making generated managed hooks prefer the captured CLI path over PATH-based commit-echo, adding an end-to-end regression test and an explicit fallback when that CLI is missing. Bounded behavior fix; no rollout, policy, schema, or contract expansion.
Re-trigger cubic



Summary
cliPathauthoritative in generated managed hookscommit-echoresolution only when the captured CLI is unavailableFixes #308