Repository navigation
chore(deps): bump silo-plugin-sdk to v0.27.0 - #19
Conversation
The catalog tool validates each plugin release with the SDK's manifest validator. v0.27.0 accepts watch-sync max_batch_size up to 1000, so a release that declares more than 100 can be added to the catalog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Problem
Related issue: N/A
The catalog tool cannot add a watch-sync plugin release that declares
max_batch_sizeabove 100.update-catalogvalidates each release's manifest with the plugin SDK, and the pinned v0.21.0 rejects it withwatch sync max_batch_size must be between 1 and 100. The MDBList watch-provider plugin is about to declare 1000.Approach
Bump
silo-plugin-sdkto v0.27.0 (Silo-Server/silo-plugin-sdk#44), which accepts 1 to 1000. The SDK's own requirements bring along newergrpc,genprotoandx/text. No catalog entries change.Automation impact:
update-catalogandupdate-manifestrun frommain, so this needs to merge before the MDBList plugin release that declares 1000.Validation
GOWORK=off go test ./...,go vet ./...,go build ./...: pass.gofmt -l .: clean.BuildPackageFromReleaseaccepts the MDBList plugin's manifest withmax_batch_size: 1000; with v0.21.0 it rejects it with the error above.Evidence
Evidence: https://evidence.siloserver.org/r/silo-plugins/pr-19/
Risks
Checklist
AI Disclosure
🤖 Generated with Claude Code