Distribution manifest format

Distribution manifests define a compatible Foundry release bundle.

Goals

• make compatible repo tags explicit
• define the verification matrix in one place
• give sites a stable upgrade target

Schema

Current manifests use schema_version: 1.

Top-level sections:

• bundle
  • release metadata for the bundle itself
• components
  • shared repos and reference repos that belong to the bundle
• verification
  • local repos and commands that must pass before the bundle is considered verified
• notes
  • human-readable release notes

Component fields

Each entry in components supports:

• id
• role
• repo
• local
• version

role is descriptive and does not change verification behavior.

Verification repository fields

Each entry in verification.repositories supports:

• name
• path
• expected_tag
• require_clean
• require_head_tag

These let release verification distinguish between:

• a repo merely containing the required tag
• a repo currently checked out exactly at the required tag

The path value should normally match a components[].local entry so automation can materialize the bundle into a clean workspace before verifying it.

Verification check fields

Each entry in verification.checks supports:

• name
• cwd
• install_command
• command

Checks run relative to the workspace root supplied to the verification script. install_command is optional and is intended for dependency installation in a clean cloned workspace before the main verification command runs.

Example

See manifests/stable/v0.2.2.yaml for the current stable bundle example.