v1.1.1

Release date: 2026-04-19

Why This Release Matters

v1.1.1 restores installer compatibility when a source repo still exposes either the legacy src/plugin.yaml tree or the current plugin/plugin.yaml tree.

What Changed For Users

• integration install detection now accepts both authored layouts during add flows
• first-party aliases such as gitlab and notion stop failing just because the upstream repo still uses the older tree
• the current plugin/ layout remains the recommended path for new repos

What This Means In Practice

• plugin-kit-ai add <source> works again across the current first-party catalog
• teams do not need to know which authored layout a source repo still carries
• the public CLI patch line regains the compatibility expected by the published install examples

Recommended Defaults After v1.1.1

• keep plugin/plugin.yaml as the canonical layout for new repos
• treat src/plugin.yaml as legacy compatibility input, not the preferred new path
• rerun failed first-party alias installs on this patched release or newer

What To Do Now

• update to v1.1.1 or newer if add gitlab or add notion failed on the published CLI
• rerun the add flow if a previous install stopped midway
• keep new repos on the standard plugin/ authoring layout

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