fix: preserve OpenClaw plugin allowlist on update#207
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughThe update and reinstall scripts now remove only ClawRouter-related entries from ChangesPlugin allow-list cleanup
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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: 1
🤖 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 `@scripts/reinstall.sh`:
- Line 217: Update the plugin filters in scripts/reinstall.sh (line 217) and
scripts/update.sh (line 230) to also exclude the capitalized 'ClawRouter'
identifier, alongside 'clawrouter' and '`@blockrun/clawrouter`'.
🪄 Autofix (Beta)
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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: e69d4196-3a67-4078-bcad-163941066ac5
📒 Files selected for processing (2)
scripts/reinstall.shscripts/update.sh
setup's OpenClaw detection was `command -v openclaw` and nothing else. npm runs lifecycle scripts with a stripped PATH, so a working global install is invisible there and setup exits telling the user to install what they already have. Verified: under `env -i PATH=/usr/bin:/bin`, `command -v openclaw` finds nothing while the binary is right there; the new fallback chain (npm_config_prefix, npm root -g, ~/.npm-global/bin, ~/.local/bin, /usr/local/bin) finds it. Added bare Gemini Pro shorthands: gemini-pro / gemini-3-pro / gemini-3.1-pro -> google/gemini-3.1-pro. `gemini-3-pro` was never a real id (the 3-series Pro shipped as -preview, then 3.1) but callers reach for it and got a 400. These are bare alias keys, so they advertise as their own /v1/models rows while the canonical google/gemini-3.1-pro catalog entry stays unshadowed -- a slash-prefixed key would have shadowed it and misadvertised the pricing. Pinned by a test. /v1/models 205 -> 208, no aliases lost. Both cherry-picked from #206, which is now closed: its cache-sync landed in v0.12.223, its allowlist fix as #207, its banner rename in v0.12.221, and its root cause was fixed properly in v0.12.225.
Summary
Tests
Summary by CodeRabbit