From e86c6367e1ad30873c1c266dc28924b51630ec11 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Wed, 19 Aug 2026 15:47:34 +0200 Subject: [PATCH] =?UTF-8?q?chore(plugin-kit):=20cut=200.4.3=20=E2=80=94=20?= =?UTF-8?q?the=20sync-engine=20changes=20plugins=20cannot=20pick=20up=20ot?= =?UTF-8?q?herwise?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two changes have been sitting in `sync-engine.ts` with no way to reach a plugin: `minInterval` (the fs-change rate cap), which v0.31.0's changelog already recorded as owing a cut, and the always-apply sync reasons — `startup` and `manual` publish even when the fingerprint matches, so an operator who fixes a host-side art-root problem recovers by restarting the runner instead of deleting the plugin's cache file. The registry skips 0.4.2 deliberately. `plugin-kit-v0.4.2` was tagged at the Steam cover-art commit but its publish never landed — the registry's newest kit is still 0.4.1 — and the tag is left exactly where it is rather than moved onto newer code. Every consumer's range is a caret (`^0.4.1`, `^0.4.2`), so 0.4.3 satisfies all of them, and the plugin that asked for `^0.4.2` gets the cover-art scan it was waiting for in the same package. --- CHANGELOG.md | 2 +- plugin-kit/package.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4b411b2c..dd954640 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -46,7 +46,7 @@ three ABIs, which removes the Compose screenshot scenes. | `api/openapi.json` | 0.29.0 | **0.29.0** | unchanged — no management-API surface moved this cycle; both copies (`api/` and `docs-site/public/`) are byte-identical to each other and to the tag | | gamescope patch level (`+pfhdrN`) | 8 | **8** | unchanged; no new patch files. ⚠ `packaging/gamescope/PKGBUILD` still says `pfhdr7` — pre-existing at v0.30.0, not a regression this cycle, but the Arch package builds a binary the host's `>= 8` probe rejects for the keymap path | | `@punktfunk/host` (SDK) | 0.1.4 | **0.1.4** | unchanged in `package.json` — but `sdk/src/config.ts` and `runner-cli.ts` changed (the `mgmt-endpoint` fix below), so a `sdk-v0.1.5` cut is **owed**; plugins resolve the SDK from the registry and cannot pick the fix up until it ships | -| `@punktfunk/plugin-kit` | 0.4.2 | **0.4.2** | unchanged in `package.json` — but `sync-engine.ts` gained `minInterval` (below), so a `plugin-kit-v0.4.3` cut is **owed** for the same reason | +| `@punktfunk/plugin-kit` | 0.4.2 | **0.4.3** | cut, for the two `sync-engine.ts` changes that cannot reach a plugin any other way: `minInterval` (below) and the always-apply sync reasons (`startup`/`manual` publish even when the fingerprint matches, so a host-side art drop is recoverable by restarting rather than by deleting the plugin's cache). Note the registry skips 0.4.2: `plugin-kit-v0.4.2` was tagged but its publish never landed, and the tag is left where it is rather than moved | ⚠ The SDK and plugin-kit version independently of the app (`sdk-v*` / `plugin-kit-v*` tags, `sdk-publish.yml` / `plugin-kit-publish.yml`); this release commit does not bump them. Both have diff --git a/plugin-kit/package.json b/plugin-kit/package.json index 689e5a27..b661292e 100644 --- a/plugin-kit/package.json +++ b/plugin-kit/package.json @@ -1,6 +1,6 @@ { "name": "@punktfunk/plugin-kit", - "version": "0.4.2", + "version": "0.4.3", "description": "Effect-based framework for punktfunk plugins: lifecycle runtime, config/state, sync engine, UI serving, CLI scaffold, and browser helpers.", "type": "module", "license": "MIT OR Apache-2.0", -- 2.54.0