chore: harden plugin boundary report · openclaw/openclaw@38ba278
steipete
·
2026-04-28
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -89,10 +89,15 @@ For external plugins, compatibility work follows this order:
|
89 | 89 | 6. remove only after the announced migration window, usually in a major release |
90 | 90 | |
91 | 91 | Maintainers can audit the current migration queue with |
92 | | -`pnpm plugins:boundary-report`. The report groups deprecated compatibility |
93 | | -records by removal date, counts local code/docs references, surfaces cross-owner |
94 | | -reserved SDK imports, and summarizes the private memory-host SDK bridge so |
95 | | -compatibility cleanup stays explicit instead of relying on ad hoc searches. |
| 92 | +`pnpm plugins:boundary-report`. Use `pnpm plugins:boundary-report:summary` for |
| 93 | +compact counts, `--owner <id>` for one plugin or compatibility owner, and |
| 94 | +`pnpm plugins:boundary-report:ci` when a CI gate should fail on due |
| 95 | +compatibility records, cross-owner reserved SDK imports, or unused reserved SDK |
| 96 | +subpaths without a dormant classification. The report groups deprecated |
| 97 | +compatibility records by removal date, counts local code/docs references, |
| 98 | +surfaces cross-owner reserved SDK imports, classifies dormant reserved SDK |
| 99 | +subpaths, and summarizes the private memory-host SDK bridge so compatibility |
| 100 | +cleanup stays explicit instead of relying on ad hoc searches. |
96 | 101 | |
97 | 102 | If a manifest field is still accepted, plugin authors can keep using it until |
98 | 103 | the docs and diagnostics say otherwise. New code should prefer the documented |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
