Cut plugin-kit 0.4.3 — the sync-engine changes plugins cannot pick up otherwise #334

2026-08-19T13:48:33Z

enricobuehler commented

2026-08-19 13:48:33 +00:00

Version bump only. This is the cut v0.31.0's changelog already recorded as owed, plus the fix from #330.

Two changes have been sitting in sync-engine.ts with no way to reach a plugin:

minInterval — the fs-change rate cap, already flagged as owing a cut.
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.

Why the registry skips 0.4.2

plugin-kit-v0.4.2 is a pushed tag, at the Steam cover-art commit, whose publish never landed — the registry's newest kit is still 0.4.1. That tag is left exactly where it is rather than force-moved onto newer code, so 0.4.2 stays a hole in the registry.

Nothing needs it to be filled: every consumer's range is a caret (^0.4.1 in playnite, ^0.4.2 in steam), so 0.4.3 satisfies all of them — and the plugin that asked for ^0.4.2 gets the cover-art scan it has been waiting for in the same package.

What this unblocks

@punktfunk/plugin-steam 0.1.2 has been merged and unreleased since 18 Aug because it depends on a kit that does not exist yet. Once this publishes, the release chain is: steam v0.1.2 → playnite v0.4.4 → the index PR pinning both.

Version bump only. This is the cut v0.31.0's changelog already recorded as owed, plus the fix from [#330](https://git.unom.io/unom/punktfunk/pulls/330). Two changes have been sitting in `sync-engine.ts` with no way to reach a plugin: - **`minInterval`** — the fs-change rate cap, already flagged as owing a cut. - **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. ## Why the registry skips 0.4.2 `plugin-kit-v0.4.2` is a pushed tag, at the Steam cover-art commit, whose publish never landed — the registry's newest kit is still **0.4.1**. That tag is left exactly where it is rather than force-moved onto newer code, so 0.4.2 stays a hole in the registry. Nothing needs it to be filled: every consumer's range is a caret (`^0.4.1` in playnite, `^0.4.2` in steam), so 0.4.3 satisfies all of them — and the plugin that asked for `^0.4.2` gets the cover-art scan it has been waiting for in the same package. ## What this unblocks `@punktfunk/plugin-steam` 0.1.2 has been merged and unreleased since 18 Aug because it depends on a kit that does not exist yet. Once this publishes, the release chain is: steam v0.1.2 → playnite v0.4.4 → the index PR pinning both.

enricobuehler added 1 commit 2026-08-19 13:48:35 +00:00

chore(plugin-kit): cut 0.4.3 — the sync-engine changes plugins cannot pick up otherwise

ci / web (pull_request) Successful in 1m12s

Details

ci / bun-nix (pull_request) Successful in 53s

Details

ci / docs-site (pull_request) Successful in 1m23s

Details

ci / rust-arm64 (pull_request) Successful in 1m35s

Details

ci / rust (pull_request) Successful in 7m35s

Details

nix / flake (pull_request) Failing after 12m52s

Details

e86c6367e1

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.

enricobuehler scheduled this pull request to auto merge when all checks succeed 2026-08-19 13:51:00 +00:00

enricobuehler merged commit f415c7d090 into main

2026-08-19 13:51:05 +00:00

enricobuehler deleted branch release-plugin-kit-0.4.3

2026-08-19 13:51:07 +00:00

enricobuehler referenced this pull request from unom/punktfunk-plugin-steam

2026-08-19 14:15:46 +00:00

Refresh bun.lock onto plugin-kit 0.4.3, so 0.1.2 can actually be released #4

enricobuehler referenced this pull request from unom/punktfunk-plugin-playnite

2026-08-19 14:28:20 +00:00

Require plugin-kit ^0.4.3, so the sync fix reaches an upgrade and not just a fresh install #9

enricobuehler referenced this pull request