From f29429789c4766692d316f8fadda71ccc7e571cc Mon Sep 17 00:00:00 2001 From: Zhi Date: Tue, 9 Jun 2026 20:06:27 +0800 Subject: [PATCH] docs: recommend --lock-write over manual lockfile editing --- AGENTS.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 52039c9f8f7..c9cd0de2de0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -52,11 +52,15 @@ with workspace members in `packages/*` and `www/`. ### Lockfile quirks -The lockfile contains remote specifiers pointing to `refs/heads/main` (e.g. -`raw.githubusercontent.com/.../refs/heads/main/...`). These hashes go stale when -upstream pushes. When that happens, manually update the hash in `deno.lock` -since `deno cache --reload` cannot fix it (see -https://github.com/denoland/deno/issues/32991). +The lockfile may contain unpinned remote specifiers whose content can change +(known limitation, see https://github.com/denoland/deno/issues/32991). If +`deno install` fails with an integrity check error, run: + + deno install --lock-write + +This tells Deno to accept the new content and update the lockfile. The +`--reload` flag alone is not sufficient here because it re-fetches content but +still validates against the existing lockfile integrity. ## Architecture