v1.1.2

Release date: 2026-04-19

Why This Release Matters

v1.1.2 fixes the Gemini part of full multi-target add flows when the source comes from a GitHub repo path or a first-party alias that resolves to one.

What Changed For Users

• Gemini installs for GitHub repo-path sources now route through the managed local projection flow
• first-party aliases such as gitlab and notion no longer break full multi-target add runs because of the Gemini lane
• the managed multi-agent install story stays aligned across the supported targets

What This Means In Practice

• plugin-kit-ai add gitlab and plugin-kit-ai add notion now complete again on the current patch line
• teams can keep using the simple first-party alias path instead of working around Gemini-specific repo-path behavior
• the current public baseline is now the patch line that covers both authored-layout compatibility and the Gemini repo-path fix

Recommended Defaults After v1.1.2

• keep first-party aliases as the normal public install path when the catalog already provides them
• keep managed repo-path installs on the current patch line or newer
• rerun full multi-target add flows on v1.1.2 or newer if Gemini previously failed

What To Do Now

• update to v1.1.2 or newer if full multi-target installs failed during the Gemini step
• rerun the add flow for affected first-party aliases
• treat v1.1.2 as the current public baseline for install guidance and examples

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