plugin-kit 0.4.1 — publish the icon field, without which no plugin can name its mark #186

Merged

enricobuehler merged 1 commits from worktree-launcher-icon-kit-release into main 2026-08-12 22:30:16 +00:00

Conversation 0 Commits 1 Files Changed 1

+1 -1

1 Commits

Author	SHA1	Message	Date
enricobuehler	d6dbb391d6	chore(plugin-kit): 0.4.1 — publish the icon field, without which no plugin can name its mark ... `ProviderEntry.icon` landed in f62a48d4 along with the token's whole supporting cast: the host-side shape guard, the seven masters, six client renderers, the SDK and the OpenAPI. What it did not get was a version bump, and the kit had cut 0.4.0 the day before. So the registry's 0.4.0 is the tarball WITHOUT the field, and it is the newest thing any plugin can resolve. A plugin that emits `icon` on a launcher entry therefore fails `tsc --noEmit` — "Object literal may only specify known properties, and 'icon' does not exist" — which is a CI gate in every plugin repo. That is why the three plugins that were supposed to carry the token never shipped it: the edits could not be committed against a kit that had no field to fill. Nothing but the version moves here. The only plugin-kit change since 0.4.0 was published is f62a48d4 itself, so 0.4.1 is exactly that commit's kit surface — one optional string on an existing struct, additive, and inert for a plugin that never sets it.	2026-08-13 00:29:26 +02:00