Promote every catalog entry to beta - #11
Merged
Merged
Conversation
All components, services, and tools in the catalog now carry `status: "beta"`; nothing remains at `experimental`. The org profile tables and the docs-site component pages both read this file, so both surfaces follow.
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.
Every entry in
components.jsonnow carriesstatus: "beta". Ten entries moved offexperimental:opcua-adapter,modbus-adapter, andedgecommonswere already beta.Downstream surfaces follow automatically — no companion edits needed:
edgecommons/.githubsync-profileregenerates the org landing-page tables from this file (daily cron +workflow_dispatch); itsSTATUSmap rendersbetaas Beta.core/website/scripts/sync-component-docs.mjsshallow-clones this repo at docs-site build time.Validation:
check-jsonschema --schemafile registry.schema.json components.json→ok(the exact commandvalidate-registryCI runs).Not changed here (call out if you want them):
registry.schema.jsonstill keeps"default": "experimental"for thestatusfield, so a new entry that omitsstatusstill lands as experimental.category: "tool"entries (ec-uns-cmd,ec-secrets) were included in "all components" — say the word if tools should stay experimental.