fix: align cold PostHog policy previews - #167
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughCold named-PostHog route previews now resolve ChangesPostHog policy parity
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Closes #166
Cold previews for a single named official PostHog upstream now evaluate the canonical
execpolicy name, matching execution after discovery.The regression deliberately avoids
listTools()and proves bothtoolRiskOverrides.execanddeny: ["exec"]produce the same blocked decision in preview and execution.Validation:
npx vitest run tests/mcp-wrapper.test.ts -t "uses the canonical exec policy name for cold named PostHog previews" --reporter=dotnpx vitest run tests/mcp-wrapper.test.ts --reporter=dotnpm run lintnpm run typechecknpm test(85 passed, 1 skipped; 1,072 passed, 23 skipped)Summary by CodeRabbit
Bug Fixes
execcalls consistently return aPOLICY_BLOCKEDerror.Tests