Skip to docs content
Migrate from type project
Open Source
Free Cloud
Pro
Updated 2026-09-03

Migrate from type project

Editions: Open Source · Free Cloud · Pro

type: project is gone. Existing project activation rows stay. Only authoring and GraphQL type semantics change.

config.yml

Before:

plugin:
  id: hc-example-plugin
  type: project

After:

plugin:
  id: hc-example-plugin
  capabilities:
    - project.graphql
    - project.rest

Production still accepts legacy type: project and maps it. Development (PLUGIN_STRICT_TYPE=1 or ENVIRONMENT=dev) errors until you declare capabilities.

GraphQL

PluginDetailsFields.type always resolves to system. Use capabilities, official, signed, and activate_status instead. Console queries dropped type.

listPluginIds(type:) still exists; the engine ignores the old project/system split and returns installed system plugins.

Protobuf

Do not reuse reserved enum numbers PLUGIN_TYPE_INTERNAL=0 and PLUGIN_TYPE_EXTERNAL=1. Handshake version unchanged.