Colony OSS Changelog

Release notes for the open-source Colony pipeline: @colony/core, @colony/sdk, @colony/cli, and all agent packages (@colony/developer, @colony/reviewer, @colony/analyzer, @colony/planner, @colony/merger).

Note

Colony OSS has not yet published a stable public release. The authoritative release history — including pre-release tags and release notes — is available at github.com/RunColony/colony/releases. This page will be updated as releases are cut.

What to expect from Colony OSS releases

Colony OSS follows semantic versioning:

• Patch releases (e.g. 0.1.1) — bug fixes and minor behavioral corrections. No migration required.
• Minor releases (e.g. 0.2.0) — new features, new configuration fields, and new SDK exports. Fully backward-compatible. Release notes include new fields and their defaults.
• Major releases (e.g. 1.0.0) — breaking changes to the configuration schema, SDK contract, or state machine. Release notes include a migration guide for every breaking change.

Pre-release development

Colony is in active pre-release development. Breaking changes may occur between pre-release versions (0.x.y). Key stabilization milestones:

• Executor contract (@colony/sdk) — stable; changes are additive and backward-compatible.
• Configuration schema (colony.config.yaml) — stable for Tier 1 and Tier 2 fields; Tier 3 fields are subject to change before 1.0.0.
• State machine — the 16-state machine is the production-validated baseline, now encoded as the bundled colony-default workflow. New workflow engine features will be additive.
• Pipeline Store schema — migrations are always forward-only; no rollback scripts are provided for pre-1.0 releases.

Versioning of Colony Cloud relative to Colony OSS

Colony Cloud ships ahead of Colony OSS tags. Colony Cloud release notes reference the OSS commit range in use at each Cloud release. See the Colony Cloud Changelog for Cloud-specific release history.