Skip to content

docs: recommend --lock-write over manual lockfile editing #3839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SisyphusZheng wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −5
Open

docs: recommend --lock-write over manual lockfile editing #3839

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading