Runtime version contract drift
Deno unsupported lockfile version 5 Deno 1.43.5 lockfile v5 introduced
A Docker image or embedded runtime can ship Deno 1.x while the application lockfile was generated for a newer Deno format. The fix is to use a Deno 2.x runtime that can read lockfile version 5.
Agent Quick Fix
# Bad for lockfile v5:
# ARG DENO_VERSION=1.43.5
# Use a Deno 2.x runtime:
ARG DENO_VERSION=2.3.0Rebuild or select an image where the bundled Deno runtime and generated lockfile version agree.
Symptom
The app install succeeds, but runtime startup fails with `Unsupported lockfile version '5'` or equivalent Deno lockfile parsing errors.
Why This Happens
The application artifact and embedded runtime are from incompatible release lines. The package manager may have succeeded; the failure appears only at first runtime launch.
Codex Search Keywords
Deno unsupported lockfile version 5 Deno 1.43.5 lockfile v5 introduced
site:github.com/denoland/deno "lockfile version 5" "Unsupported lockfile"
"Unsupported lockfile version '5'"
https://raw.githubusercontent.com/denoland/deno/v1.43.5/cli/args/lockfile.rs
https://raw.githubusercontent.com/denoland/deno/v2.0.0/cli/args/lockfile.rs