Contribute to the registry

The public registry lives in bricoop-releases and holds every published application and provider manifest. Contributing an integration means authoring the manifest, validating it locally, and opening a reviewable pull request; on merge, a release manifest is published and Bricoop Desktop picks it up. The workflow is the same for new integrations and for updates to existing ones.

Repository structure

bricoop-releases holds applications/ and providers/ directories. Each integration has its own subdirectory containing a metadata.yaml with display and ownership information, a stable.yaml with the pinned manifest Bricoop reads at runtime, and the schema files the validator uses. Adding an integration means adding a subdirectory; updating one means editing the files already present.

Validation

Run the repository’s validation before submitting. The validator checks the manifest against the schema, verifies the stable ID matches the directory, and rejects any unknown field because the schema is strict. Fix every reported issue before opening a pull request; the same validation runs in CI and will block the merge until the manifest is clean.

Pull requests and releases

Open a reviewable pull request against bricoop-releases with your manifest changes. A maintainer reviews the PR; on merge, the release pipeline publishes a new release manifest and Bricoop Desktop picks it up on the next update check. See the registry lifecycle page for how an integration moves from proposal through maintenance to deprecation and removal.