feat(plugins): source the plugin registry from Tabularium and link the live registry - #14
Open
NewtTheWolf wants to merge 1 commit into
Open
feat(plugins): source the plugin registry from Tabularium and link the live registry#14NewtTheWolf wants to merge 1 commit into
NewtTheWolf wants to merge 1 commit into
Conversation
…e live registry - fetch-app-data merges the legacy plugins/registry.json (app repo) with the Tabularium registry API (registry.tabularis.dev, kind=driver); Tabularium wins per plugin id, marked COMPAT(registry-ga) until every plugin lives there - asset links use the registry's tracked download URLs so website downloads count in the registry analytics; legacy-only fallback if the API is down - Tabularium plugins carry registry_url: plugin names on /plugins, the :::plugin::: card and search results link to the live registry plugin page - /plugins CTA links the registry's plugin development docs next to the guide - 307 redirects: /wiki/plugins -> registry schema docs, /wiki/building-plugins -> registry plugin-development docs
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
/pluginspage (and everything else readingplugins/registry.json) was still fed exclusively from the legacy static registry in the app repo, while the app itself already defaults to the Tabularium registry atregistry.tabularis.dev. Visible drift on the live site: firestore shown as 0.1.0 (registry: 0.5.0), cloudflare-d1 0.1.0 (registry: 0.1.3), mongodb 0.1.0 (registry: 0.1.1).What changed
scripts/fetch-app-data.mjsGET registry.tabularis.dev/api/plugins?kind=driver(paginated) + one detail call per plugin are merged into the legacyplugins/registry.jsonshape; Tabularium wins per plugin id. MarkedCOMPAT(registry-ga)— once every plugin lives in Tabularium, drop the legacy fetch./api/plugins/{id}/releases/{version}?os=…&arch=…&redirect=1), so website downloads show up in the registry analytics. Verified live: 302 → author's release asset./pluginspage,:::plugin:::markdown cards, search index) are untouched: they keep reading the same legacy-shaped JSON.Live registry links
registry_url; the plugin name on/plugins, the:::plugin:::card and search results now link toregistry.tabularis.dev/plugins/{id}. The "Repo →" button keeps pointing at the source repo./pluginsCTA now offers the registry's plugin development docs alongside the GitHub plugin guide (JSON-RPC protocol + Rust skeleton still only live there).vercel.jsonredirects (307, deliberately not permanent yet)/wiki/plugins→https://registry.tabularis.dev/docs/plugin-development/schema/wiki/building-plugins→https://registry.tabularis.dev/docs/plugin-developmentReview notes
permanenttotrue.latest_versionhas a matching release entry; search index contains the registry URLs;tsc --noEmitonly shows the 4 pre-existing errors innotes/datagrid-bench/.informixisapprovedin Tabularium but missing from/api/plugins— it is still served via the legacy merge. Likely the manifest fails the registry's current schema validation.