docs(registry): fix stale registry links, document current publish rules - #17
Open
NewtTheWolf wants to merge 1 commit into
Open
docs(registry): fix stale registry links, document current publish rules#17NewtTheWolf wants to merge 1 commit into
NewtTheWolf wants to merge 1 commit into
Conversation
- codeberg.org/Tabularium/Tabularium -> github.com/TabularisDB/tabularium; dead TabularisDB/tabularis-website repo link -> TabularisDB/website - plugin-development: '.tabularium is the single canonical manifest' (replaces the outdated two-manifests story), release-asset requirement (default.tabularium rename), 422 hard-reject, absolute /requests link, pointer to the always-current generated page + docs.tabularium.wiki - plugins: registry validation rules block (name slug, version == tag minus v, 280-char description cap), fixed invalid .tabularium examples (legacy id / display name) - configuration: document tabulariumRegistryUrl (customRegistryUrl is a read-once legacy migration field) - roadmap/plugin-registry: mark shipped as Tabularium with delivered links - home: link the hosted registry
|
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.
Follow-up to the Tabularium cutover: the wiki still pointed at the old Codeberg mirror and told the pre-cutover story.
Link fixes
codeberg.org/Tabularium/Tabularium→github.com/TabularisDB/tabularium(source + issues)TabularisDB/tabularis-websiteregistry.json link →TabularisDB/websitetabularis.devwas named as a registry instance — the instance isregistry.tabularis.devdocs.tabularium.wiki(publishing/manifest/deploy) are now actually linked from the plugin pagesFactual updates (verified against the Tabularium source)
.tabulariumis the single canonical manifest (host + registry); the "two manifests, two purposes" section was outdated. Publishing now includes the standalone release-asset requirement (GitHub renames the dotfile todefault.tabularium; the registry accepts both) and the HTTP 422 hard-reject on invalid manifests.nameslug pattern (pinned at first submit),version== release tag minusv,description≤ 280 chars. Fixed.tabulariumexample snippets that still used legacyid/ displayname.tabulariumRegistryUrl(with default);customRegistryUrlis a read-once legacy migration field.registry.tabularis.dev) rather than an Open VSX adaptation.