Registry lifecycle

Every integration in the registry follows the same lifecycle: it is proposed, merged, maintained, and eventually deprecated or removed. The lifecycle keeps the registry honest about what Bricoop actually supports, so users never connect an integration that no longer works. Each stage has a clear owner and a clear action; nothing drifts silently.

Ownership

Each integration has a maintainer responsible for its manifest. The maintainer keeps the manifest’s metadata.yaml contact fields current, responds to issues reported against the integration, and ships version bumps when the upstream application or provider changes. Ownership is declared in the manifest, not implied; an integration without a declared maintainer cannot ship.

Maintenance

Maintenance covers version bumps, new models and capabilities, and compatibility updates. When an upstream application or provider releases a breaking change, the maintainer updates the manifest’s version, minimal_client_version, or minimal_application_version and opens a pull request. The validator runs against the updated manifest before merge, so a maintenance PR is treated exactly like a new integration.

Deprecation

A deprecated integration keeps working but is flagged in the catalog and no longer promoted. Deprecation is declared in the manifest, not applied retroactively; the maintainer sets the deprecation flag and writes a reason. Users who already connected the integration can keep using it, but new users see the deprecation before they connect.

Removal

Removal is the last stage and only happens when an integration is broken, abandoned, or replaced. The removal criteria require that the integration no longer works for the majority of users, or that the maintainer has stopped responding and no replacement owner can be found. Removal ships as a release that deletes the manifest subdirectory; Bricoop Desktop stops offering the integration on the next update check.

Emergency security action

A security issue in an integration bypasses the normal release cadence. The maintainer (or a Bricoop maintainer, if the integration owner is unreachable) ships an emergency manifest that disables or removes the integration immediately, then back-fills the normal review. The emergency path exists so a vulnerable integration cannot keep running while a standard PR moves through review.