Publishing

Prerequisites

• Write access to calab-ai/apm-registry
• gh-calab extension installed
• Your primitive or package authored according to the registry schema

Publish a Primitive

gh calab apm publish primitive <type>/<name>

Example — publish a new agent:

gh calab apm publish primitive agents/my-agent

This command:

1. Validates the primitive manifest against the registry schema
2. Bumps the version (semver)
3. Opens a PR in calab-ai/apm-registry
4. On merge, triggers a GA release and updates portal-data.json

Publish a Package

gh calab apm publish package <name>

Example:

gh calab apm publish package my-workspace-bundle

Packages must reference at least one existing primitive by its apm_ref.

Versioning

APM uses semantic versioning (MAJOR.MINOR.PATCH):

• PATCH — backwards-compatible changes (doc updates, minor fixes)
• MINOR — new optional fields or behaviours
• MAJOR — breaking changes (renamed fields, removed types)

Review Process

All publish PRs go through automated schema validation (validate.yml in apm-registry) and require at least one human review before merge.