Skip to content

CCO compatibility in the customer portal

cco-compatibility.json declares supported CCO editions and feature packs for new product releases. Keep it with the release source commit and review it when the supported versions change. The release publisher sends this JSON to the portal alongside the product version. Existing portal releases retain their own metadata; a duplicate publish (HTTP 409) does not update them.

The MCP server supports the on-premise FP21 Manager and Cloud Edition 3.x. Each of the tags below documents both editions in its README, including the Cloud OAuth configuration and live regression tests. The previous FP21-only portal declaration omitted that Cloud support.

Portal 0.8.0 adds managerVersions: ["CLOUD_3"] for the Manager API. This is separate from POS feature packs: a Cloud Manager connection does not declare that a POS plugin works on a specific or future POS feature pack. The catalog shows "Cloud Edition 3.x (Manager)" and filters it with cco=MANAGER%3ACLOUD_3. The publish job checks the cco-manager-compatibility capability before sending this field, so an older portal cannot silently discard it.

The portal currently records editions and feature packs, not individual patch levels. Only declare a whole feature pack when that support can be stated; do not infer support from a build dependency alone.

Existing releases reviewed on 2026-09-14

  • v0.6.0 (ecbd3665efb0): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v0.7.0 (ae4a3a55ab7f): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v0.8.0 (b105ccffda1f): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v1.0.0 (dbbc5d0c0bb1): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v1.1.0 (7088c7951e2d): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v1.1.1 (cdf58f59ac42): ON_PREMISE FP21 + CLOUD_3 (Manager API)
  • v1.1.2 (27302f6fb8ef): ON_PREMISE FP21 + CLOUD_3 (Manager API)

Evidence: each tagged README documents "Cloud Edition 3.x", the IAS OAuth setup, and live checks against FP21 and Cloud (images on 2026-07-20 and reporting on 2026-08-07). These declarations describe supported editions; individual tools may have documented edition restrictions, such as on-premise-only job APIs.

Unknown or unlisted targets are not a claim of incompatibility. They need a confirmed support declaration before being added to the portal filter.