Colony OSS Changelog
Release notes for the open-source Colony pipeline: @colony/core, @runcolony/sdk, @colony/cli, and all agent packages (@colony/developer, @colony/reviewer, @colony/analyzer, @colony/planner, @colony/merger).
What to expect from Colony OSS releases
Section titled “What to expect from Colony OSS releases”Colony OSS follows semantic versioning. Every Colony package except @runcolony/sdk shares one version number, and releases come as a monthly train.
- Patch releases (e.g.
0.3.1): critical and security fixes only. No migration required. - Minor releases (e.g.
0.4.0): new features, configuration fields and SDK exports. Before1.0.0, a minor release can also contain breaking changes; each one is listed under Breaking in the release notes with the steps to migrate. - Major releases (e.g.
1.0.0): from1.0.0on, breaking changes to the configuration schema, CLI, slash commands, inbound labels, MCP tools or the container deployment surface wait for a major release.
A deprecated setting, command or tool keeps working, with a warning where Colony can show one, for at least two releases before it is removed. The release that deprecates it names the release that removes it.
Versioning of Colony Cloud relative to Colony OSS
Section titled “Versioning of Colony Cloud relative to Colony OSS”Colony Cloud has its own version numbers, named by month (cloud-v2026.11.0). Each Colony Cloud release bundles exactly one tagged Colony release and names it in its release notes, along with the Colony changes that need your attention. See the Colony Cloud Changelog.