v1.1.0

Release date: 2026-04-18

Why This Release Matters

v1.1.0 is a hardening release for teams that treat the repo as the owner of agent integration state. It does not change the default recommended path, but it makes add, update, and remove flows easier to trust across the supported multi-agent setup.

What Changed For Users

• repo-owned integration lifecycle flows now have stronger end-to-end verification across Claude, Codex, Cursor, and OpenCode managed paths
• the public release surface now points to one consistent v1.1.0 baseline across docs, starters, and helper-package pins
• runtime-package upgrade smoke now checks promotion into the current public package version instead of stopping on the earlier patch line

What This Means In Practice

• if your repo manages agent config for more than one target, add, update, and remove operations are now exercised more realistically before release
• if your team follows the public docs or starter READMEs, the visible version pins now match the current published baseline instead of mixing older values
• if you publish or hand off starter-based repos, the release story is easier to explain because the baseline, docs, and package pins now line up

Recommended Defaults After v1.1.0

• keep Go as the default when you want the strongest general production path
• use Node or Python shared runtime-package paths when those repo-local interpreted lanes are intentional for the team
• treat repo-owned managed integrations as a validated lifecycle when your repo owns agent setup

What To Do Now

• refresh any copied docs or starter snippets that still mention v1.0.6
• if you rely on repo-owned integration setup across agents, rerun your normal add, update, and remove workflow against v1.1.0
• if you are starting fresh, use the current starter pins and this release note as the baseline

Pair this release with Installation, Team-Ready Plugin, and Install Channels.