fix(video-renderer): regenerate pnpm-lock.yaml for the producer pin

The 0.7.36 exact-pin landed via an npm install, which wrote a stray
package-lock.json and left pnpm-lock.yaml stale — the image build's
pnpm install --frozen-lockfile then correctly refused the spec
mismatch, blocking deploys. Lockfile regenerated with the Dockerfile's
own pinned pnpm@11.10.0 (resolves @hyperframes/producer@0.7.36 exactly,
frozen-lockfile install and the sidecar's node --test 15/15 verified
locally); the npm lockfile is removed — this package is pnpm-managed.
This commit is contained in:
Renn F
2026-07-17 05:43:34 +02:00
parent c33a03f2aa
commit a12fefcba9
2 changed files with 1 additions and 3623 deletions
-3622
View File
File diff suppressed because it is too large Load Diff
+1 -1
View File
@@ -12,7 +12,7 @@ importers:
specifier: ^0.7.36
version: 0.7.36
'@hyperframes/producer':
specifier: ^0.7.36
specifier: 0.7.36
version: 0.7.36
express:
specifier: ^5.0.0