Getting StartedOwnable model, workflow, and first local install 2
LayoutInstallable layout wrappers with local source ownership 6
OverlayInstallable overlay wrappers with local source ownership 3
FeedbackInstallable feedback wrappers with local source ownership 5
FormInstallable form components 11
UtilityInstallable utility wrappers with local source ownership 6
NavigationInstallable navigation components 6
ToolingCLI and registry contracts 2
ReleasePublishing and workflow structure for the ownable surface 1

Release Workflow

TailNG publishes the ownable surface through a dedicated manual release flow so registry and CLI changes can be validated independently from the larger package set.

Manual ownable release

The dedicated workflow publishes only @tailng-ui/registry and tailng, with the same release phases as the main production workflow.

Test gates before publish

  • registry specs
  • CLI specs
  • docs ownable-install component specs
  • registry, CLI, and docs typechecks
  • packed CLI smoke test after build

Workflow split

The general production workflow now excludes registry and CLI targets. Ownable publishing stays isolated in its own release file so the publish surface is explicit.

Troubleshooting trusted publishing

Trusted publishing is sensitive to workflow identity. If publishing fails, verify the npm trusted publisher entry matches the exact workflow filename and environment used by the manual ownable release.