chore(registry): publish marketplace registry update - #670
Conversation
| { | ||
| "version": "0.2.4", | ||
| "manifest_url": "https://streamkit.dev/registry/plugins/servo/0.2.4/manifest.json", | ||
| "signature_url": "https://streamkit.dev/registry/plugins/servo/0.2.4/manifest.minisig", | ||
| "published_at": "2026-07-26" | ||
| }, |
There was a problem hiding this comment.
🔍 Version 0.2.3 skipped in servo release history
The registry jumps from 0.2.2 (published 2026-07-25) straight to 0.2.4, and there is no 0.2.3 directory under dist/registry/plugins/servo/ or docs/public/registry/plugins/servo/. plugins/native/servo/Cargo.toml is already at 0.2.4, so this appears to be a deliberate version bump (a 0.2.3 tag/build likely failed or was never published) rather than a missing publish step — worth a quick confirmation that no 0.2.3 release artifact exists on GitHub that clients could be pointed at.
Was this helpful? React with 👍 or 👎 to provide feedback.
Debug
| "bundle": { | ||
| "url": "https://github.com/streamer45/streamkit/releases/download/plugin-servo-v0.2.4/servo-0.2.4-bundle.tar.zst", | ||
| "sha256": "1f2f0927780dcb229b441290a11a8aacaa0293e4c8db6bf6e66b5be365930d5f", | ||
| "size_bytes": 50752188 | ||
| }, |
There was a problem hiding this comment.
📝 Info: dist and docs registry copies stay byte-identical
Verified that dist/registry/index.json and docs/public/registry/index.json are byte-identical after this change, and the corresponding new 0.2.4/manifest.json and manifest.minisig files are duplicated identically in both trees, matching the existing publishing convention. The manifest field set also matches the prior 0.2.2 manifest exactly except for the version-derived fields (version, bundle URL, sha256, size_bytes). The bundle digest/size cannot be verified from the repo — that relies on the publishing workflow.
Was this helpful? React with 👍 or 👎 to provide feedback.
Automated registry metadata update from run
30210229094.Devin Review
5bd2de8