Harness configuration types
Committed and resolved release-harness configuration models.
IMPORTANT: Developer documentation for the current development branch. This content is unreleased, may change without notice, and must not be treated as Buildish release documentation.
This section contains generated reference material for the typed Buildish Release Tooling contracts.
The generated reference intentionally includes both:
release-config.yaml, candidate, vote-package, and release
manifests, verify-rc report JSON, and inspect-repro --jsonInternal command action manifests are documented here for maintenance and debugging, but they are explicitly unstable and are not a supported external API.
The detailed generated reference is intentionally split across multiple pages so the schema and field-level contract pages stay navigable.
Committed and resolved release-harness configuration models.
Harness scenario inputs, mocked tool behavior contracts, and machine-readable run results.
Small runtime payloads used by the harness shim to emulate GitHub and other tools.
Machine-readable command action manifests written for workflow coordination. These are Buildish-owned internal input/output contracts and are intentionally unstable.
Consumer-owned and component-owned authored configuration models, including release-config.yaml and local verify-rc override payloads.
Generated contract-file tables for supported and internal Buildish Release Tooling schemas.
Typed Buildish release manifests, emitted verification reports, inspection-bundle payloads, and related helper contracts.
This reference is generated from the Buildish Release Tooling Pydantic models and checked-in reference metadata. Do not edit it by hand; regenerate it with make schemas.
Generated scalar alias, literal-set, and enum reference for Buildish Release Tooling contracts.