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

2026-08-19T14:15:46Z

enricobuehler commented

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

0.1.2 has been merged and unreleased since 18 Aug. Two things were in the way, and this fixes the one that lives here.

The lockfile was never regenerated. #3 moved the dependency range to ^0.4.2, but bun.lock 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 a v0.1.2 tag would have died in the build gate and again in publish.

The kit it wanted did not exist. The registry's newest kit was 0.4.1; plugin-kit-v0.4.2 was tagged but its publish never landed. Rather than force-move a pushed tag, the kit was cut as 0.4.3 (unom/punktfunk#334), which is now published and which ^0.4.2 accepts. It carries the same findLocalArtFile cover-art scan 0.1.2 was written against, plus the always-apply sync reasons.

Only bun.lock changes. Gates on the refreshed tree: typecheck clean, 10/10 tests, biome clean, bundle builds both entry points.

Merging this unblocks the v0.1.2 tag, and after it the index PR that pins 0.1.2 for the store.

0.1.2 has been merged and unreleased since 18 Aug. Two things were in the way, and this fixes the one that lives here. **The lockfile was never regenerated.** #3 moved the dependency range to `^0.4.2`, but `bun.lock` 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 a `v0.1.2` tag would have died in the build gate and again in publish. **The kit it wanted did not exist.** The registry's newest kit was 0.4.1; `plugin-kit-v0.4.2` was tagged but its publish never landed. Rather than force-move a pushed tag, the kit was cut as **0.4.3** ([unom/punktfunk#334](https://git.unom.io/unom/punktfunk/pulls/334)), which is now published and which `^0.4.2` accepts. It carries the same `findLocalArtFile` cover-art scan 0.1.2 was written against, plus the always-apply sync reasons. Only `bun.lock` changes. Gates on the refreshed tree: typecheck clean, 10/10 tests, biome clean, bundle builds both entry points. Merging this unblocks the `v0.1.2` tag, and after it the index PR that pins 0.1.2 for the store.

enricobuehler added 1 commit 2026-08-19 14:15:47 +00:00

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

ac4426eda6

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.

enricobuehler scheduled this pull request to auto merge when all checks succeed 2026-08-19 14:16:32 +00:00

enricobuehler merged commit 3e5b1648ae into main

2026-08-19 14:16:36 +00:00

enricobuehler deleted branch chore/lockfile-kit-0.4.3

2026-08-19 14:16:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unom/punktfunk-plugin-steam#4