v1.0.6
Release date: 2026-03-30
Why This Release Matters
v1.0.6 is the release where shared runtime packages became the clear public path for Python and Node teams instead of a half-supported workflow.
What Changed For Users
plugin-kit-ai initcan now scaffold Python and Node projects around--runtime-package- the shared
plugin-kit-ai-runtimepath is now a supported path for the approved Python and Node options - starter templates and public examples were refreshed to match the current recommended setup
- release verification and version-sync checks were tightened so the published release stays aligned with the documented install path
What This Means In Practice
- if your team wants the main non-Go path, Node/TypeScript plus
--runtime-packageis now the recommended choice - if your team is Python-first and staying repo-local, the shared runtime package is now the preferred supported path
doctorand runtime requirement messaging are clearer, so environment failures are easier to catch before blaming the project
Recommended Defaults After v1.0.6
- choose Go when you want the strongest production path and the least downstream bootstrap friction
- choose Node/TypeScript with
--runtime-packagewhen you want the main non-Go supported path - choose Python with
--runtime-packagewhen the project is repo-local and the team is intentionally Python-first
What To Do Now
- if you already use Python or Node, re-check whether
--runtime-packageis now the better default for your repo - if you still rely on vendored helper files as the long-term default, compare that setup against the current
plugin-kit-ai-runtimeguidance - if you are starting fresh, the defaults above are the simplest place to begin
Pair this release with Installation, Choosing Runtime, and Install Channels.