Runtime artifact version drift
Deno unsupported lockfile version 5 Deno 1.43.5 lockfile v5 introduced
A Docker image ships Deno 1.43.5 while the app lockfile requires Deno lockfile version 5.
Agent Quick Fix
The local repository can expose the failure, but the decisive repair depends on the current host, package, runtime, or API contract.
Product: Rocket.Chat
Current-contract area: Deno unsupported lockfile version 5 Deno 1.43.5 lockfile v5 introduced
Likely root cause: A Docker image ships Deno 1.43.5 while the app lockfile requires Deno lockfile version 5.
Repair direction: Use the source trail below to align the local install, host, API, or runtime configuration with the current external contract.
Validation Status
Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.
Symptom
A Docker image ships Deno 1.43.5 while the app lockfile requires Deno lockfile version 5.
Why This Happens
The local repository can expose the failure, but the decisive repair depends on the current host, package, runtime, or API contract.
Verification
Use the source trail below to align the local install, host, API, or runtime configuration with the current external contract.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Deno unsupported lockfile version 5 Deno 1.43.5 lockfile v5 introduced
Rocket.Chat Docker Deno 1.43.5 lockfile version 5 Deno 2 apps-engine
Deno lockfile version 5 unsupported
Source Trail
GitHub source file/reference: