v1.0.6

Release date: 2026-03-30

Why This Release Matters

v1.0.6 is the release where shared runtime-package delivery became a real public path for Python and Node teams instead of a partial or caveated workflow.

What Changed For Users

• plugin-kit-ai init can now scaffold Python and Node projects around --runtime-package
• the shared plugin-kit-ai-runtime path is treated as a supported delivery model for the approved Python and Node lanes
• starter templates and public examples were refreshed to use the current pinned versions and the clearer runtime-package story
• release verification and version-sync checks were tightened so the published surface stays aligned with the documented install path

What This Means In Practice

• if your team wants the mainstream non-Go stable lane, Node/TypeScript plus --runtime-package is now a first-class recommendation
• if your team is Python-first and staying repo-local, the shared runtime package is now the preferred supported path over vendored helper drift
• doctor and runtime requirement messaging are stronger, so environment failures are easier to catch before blaming the authored 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-package when you want the mainstream non-Go stable lane
• choose Python with --runtime-package when the project is repo-local and the team is intentionally Python-first

Migration Callout

If you previously treated vendored runtime helper files as the default long-term model for Python or Node, re-check the current guidance. For the approved shared-package lanes, plugin-kit-ai-runtime is now the clearer supported path.

Pair this release with Installation, Choosing Runtime, and Install Channels.