fix: downgrade deno lockfile v5 to v4 on read#673
Merged
nyannyacha merged 2 commits intomainfrom Mar 12, 2026
Merged
Conversation
kallebysantos
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Enhancement
Description
Currently,
deno_lockfileis pinned at 0.23.2, which only supports up to v4.Newer versions of Deno (2.2+) generate v5 lockfiles, causing a hard error on bundle.
This PR pre-processes the v5 lockfile content before passing it to
Lockfile::new, mergingoptionalDependenciesintodependenciesand stripping v5-only fields (os,cpu,tarball,deprecated,scripts,bin,optionalPeers).