Repository navigation
Code Review Workspace 1.10.1
·
136 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Other plugins start a review of a thread's changes through the same contract they read reviews by. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.10.1. 1.10.1 adds no migration, so rolling back to 1.10.0 keeps everything; reviewThreadChanges answers the same there, though BB's RPC discovery doesn't list it.
reviewThreadChanges, which Review changes above a thread's message box calls, is part of the contract other plugins rely on, docs/plugin-api.md, where it was the panel's own and could change without notice. It keeps its name, takes{ threadId }and answers{ ok, error, targetKey }, as since 1.8.0; its answer may gain fields. BB's RPC discovery lists it besidereviews.v1.status, each field described. Calling it starts a review, so a plugin doesn't probe it: whereverreviews.v1.statusanswers, it does.- docs/plugin-api.md says what it starts or opens, what that costs, and why it refuses; and that on Postgres storage
reviews.v1.statusanswersunknown_methodfor a moment as Code Review Workspace starts, so a plugin asks again on its next poll rather than remember it.