openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@00e30ba8d9

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-28 03:15:04 +00:00
parent a62f4dcf91
commit b94f6fb80b
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "ae616777f3b185d7e12da4e1dac999bf0ace8bb5",
"syncedAt": "2026-04-28T03:11:54.887Z"
"sha": "00e30ba8d90f5398f11688bef3e317ef15b0cf90",
"syncedAt": "2026-04-28T03:13:34.985Z"
}

6
docs/plugins/sdk-migration.md
View File

@ -88,6 +88,12 @@ For external plugins, compatibility work follows this order:
5. document the deprecation and migration path
6. remove only after the announced migration window, usually in a major release
Maintainers can audit the current migration queue with
`pnpm plugins:boundary-report`. The report groups deprecated compatibility
records by removal date, counts local code/docs references, surfaces cross-owner
reserved SDK imports, and summarizes the private memory-host SDK bridge so
compatibility cleanup stays explicit instead of relying on ad hoc searches.
If a manifest field is still accepted, plugin authors can keep using it until
the docs and diagnostics say otherwise. New code should prefer the documented
replacement, but existing plugins should not break during ordinary minor