Merge pull request 'Refresh bun.lock onto plugin-kit 0.4.3, so 0.1.2 can actually be released' (#4 ) from chore/lockfile-kit-0.4.3 into main

chore: refresh bun.lock onto plugin-kit 0.4.3, so 0.1.2 can actually be released
0.1.2 moved the dependency range to `^0.4.2` but the lockfile was never regenerated: it still carried `^0.4.1` and resolved kit 0.4.1. Both CI jobs run `bun install --frozen-lockfile`, which fails outright when the lock disagrees with package.json — so the build gate and the publish job would both have died on a `v0.1.2` tag. The lock now resolves 0.4.3. The registry has no 0.4.2 at all: that tag's publish never landed, and rather than move a pushed tag the kit was cut as 0.4.3, which this range accepts and which carries the same `findLocalArtFile` cover-art scan 0.1.2 was written against. Gates on the refreshed tree: typecheck clean, 10/10 tests, biome clean, bundle builds both entry points.
2026-08-19 14:16:34 +00:00 · 2026-08-19 16:14:56 +02:00 · 2026-08-18 20:22:36 +00:00 · 2026-08-16 08:46:19 +00:00
2 changed files with 4 additions and 4 deletions
@@ -5,7 +5,7 @@
    "": {
      "name": "@punktfunk/plugin-steam",
      "dependencies": {
-        "@punktfunk/plugin-kit": "^0.4.1",
+        "@punktfunk/plugin-kit": "^0.4.2",
        "effect": "4.0.0-beta.99",
      },
      "devDependencies": {
@@ -48,7 +48,7 @@

    "@punktfunk/host": ["@punktfunk/host@0.1.3", "https://git.unom.io/api/packages/unom/npm/%40punktfunk%2Fhost/-/0.1.3/host-0.1.3.tgz", { "optionalDependencies": { "undici": "^7.0.0" }, "peerDependencies": { "effect": "^4.0.0-beta.98" }, "bin": { "punktfunk-scripting": "dist/runner-cli.js" } }, "sha512-WpS0a3yavoqDBA3V8xSZW298HRUzF8TFuwSKf3hV1RFHZ2lM6V77E6mFJTej3p+B1wnNWzphtlY+WgcsUx/34A=="],

-    "@punktfunk/plugin-kit": ["@punktfunk/plugin-kit@0.4.1", "https://git.unom.io/api/packages/unom/npm/%40punktfunk%2Fplugin-kit/-/0.4.1/plugin-kit-0.4.1.tgz", { "peerDependencies": { "@punktfunk/host": "^0.1.3", "effect": "^4.0.0-beta.98", "react": "^19.2.0" }, "optionalPeers": ["react"] }, "sha512-yqDF9Zrt9IFbL3bCSjIUOW4abSltMKaL+vdljyUmA2rEeHzcYudVOczrE7S5Q6kipOkC5FoiCfjV8xwGBW2UUQ=="],
+    "@punktfunk/plugin-kit": ["@punktfunk/plugin-kit@0.4.3", "https://git.unom.io/api/packages/unom/npm/%40punktfunk%2Fplugin-kit/-/0.4.3/plugin-kit-0.4.3.tgz", { "peerDependencies": { "@punktfunk/host": "^0.1.3", "effect": "^4.0.0-beta.98", "react": "^19.2.0" }, "optionalPeers": ["react"] }, "sha512-WZGKmkm3qthFGdCQuB9dqh1YpPCJN9SBiWd76FdBS4mp9Uh/rYiT3DSWLXr0hXPYPzX7E1Dt/oD6hd1SemGUSA=="],

    "@standard-schema/spec": ["@standard-schema/spec@1.1.0", "", {}, "sha512-l2aFy5jALhniG5HgqrD6jXLi/rUWrKvqN/qJx6yoJsgKhblVd+iqqU4RCXavm/jPityDo5TCvKMnpjKnOriy0w=="],

@@ -1,6 +1,6 @@
 {
 	"name": "@punktfunk/plugin-steam",
-	"version": "0.1.1",
+	"version": "0.1.2",
 	"private": false,
 	"type": "module",
 	"description": "Punktfunk plugin: adds your installed Steam games and non-Steam shortcuts to the host library, with their art and Big Picture.",
@@ -36,7 +36,7 @@
 		"check": "bunx biome check ."
 	},
 	"dependencies": {
-		"@punktfunk/plugin-kit": "^0.4.1",
+		"@punktfunk/plugin-kit": "^0.4.2",
 		"effect": "4.0.0-beta.99"
 	},
 	"devDependencies": {
Author	SHA1	Message	Date
enricobuehler	3e5b1648ae	Merge pull request 'Refresh bun.lock onto plugin-kit 0.4.3, so 0.1.2 can actually be released' (#4 ) from chore/lockfile-kit-0.4.3 into main CI / build (push) Failing after 11m42s Details CI / publish (push) Skipped Details	2026-08-19 14:16:34 +00:00
enricobuehler	ac4426eda6	chore: refresh bun.lock onto plugin-kit 0.4.3, so 0.1.2 can actually be released CI / build (pull_request) Successful in 19s Details CI / publish (pull_request) Skipped Details 0.1.2 moved the dependency range to `^0.4.2` but the lockfile was never regenerated: it still carried `^0.4.1` and resolved kit 0.4.1. Both CI jobs run `bun install --frozen-lockfile`, which fails outright when the lock disagrees with package.json — so the build gate and the publish job would both have died on a `v0.1.2` tag. The lock now resolves 0.4.3. The registry has no 0.4.2 at all: that tag's publish never landed, and rather than move a pushed tag the kit was cut as 0.4.3, which this range accepts and which carries the same `findLocalArtFile` cover-art scan 0.1.2 was written against. Gates on the refreshed tree: typecheck clean, 10/10 tests, biome clean, bundle builds both entry points.	2026-08-19 16:14:56 +02:00
enricobuehler	88e4cc84ae	Merge pull request '0.1.2 on kit 0.4.2 — the cover-art scan a host cannot pick up any other way' (#3 ) from chore/kit-0.4.2-cover-art-names into main CI / build (push) Failing after 19s Details CI / publish (push) Skipped Details Reviewed-on: #3	2026-08-18 20:22:36 +00:00
enricobuehler	50316d3fdf	chore: 0.1.2 on kit 0.4.2 — the cover-art scan a host cannot pick up any other way CI / build (pull_request) Failing after 22s Details CI / publish (pull_request) Skipped Details plugin-kit 0.4.2 teaches `findLocalArtFile` the names and layouts Steam actually uses today: `library_capsule.jpg` beside `library_600x900.jpg`, `header.jpg` beside `library_header.jpg`, and the `<appid>/<name>` layout that holds 623 of the 779 appids on the reference cache. Measured there, per-appid art found locally goes portrait 25 -> 328 and header 86 -> 716, with no appid losing art it already had. The range moves to ^0.4.2 rather than resting on ^0.4.1 admitting it. A host's plugins dir has its own bun.lock pinning the NESTED kit copy, so `bun add @punktfunk/plugin-steam@0.1.2` under the old range is free to keep the 0.4.1 it already has — which is exactly the state found on the .41 box, where patching the hoisted kit did nothing because the plugin resolves its own nested one. Nothing in this repo's own source changes: the kit is external at build time, so this is the version bump that lets the fix travel.	2026-08-16 08:46:19 +00:00