Repository navigation
feat: migrate to the .tabularium manifest for the Tabularium registry - #2
Merged
Merged
Conversation
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
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.
Migrates this plugin from the legacy
manifest.jsonto the canonical.tabulariumbundle manifest that the Tabularis host now reads and the hosted Tabularium registry requires (the registry resolves the manifest from release assets, so.tabulariummust be published as a standalone asset).Generated with
@tabularis/create-plugin migrate..tabulariumwritten frommanifest.json;manifest.jsonremovedjustfile/README.mdreferences renamed.github/workflows/release.ymlregenerated from the registry-ready template (--ci): builds all five platforms and publishes.tabulariumas a standalone release asset — re-apply any custom CI steps if there were anyidkept (differs fromname, so it is the plugin identity)