@pnpm/lockfile.utils 1100.0.5 → 1100.0.7

package/lib/toLockfileResolution.js

@@ -3,12 +3,18 @@ export function toLockfileResolution(pkg, resolution, registry, lockfileIncludeT
     if (resolution.type !== undefined || !resolution['integrity']) {
         return resolution;
     }
+    // Tarball-typed resolutions are guaranteed to carry a tarball URL by the
+    // resolver, but guard for unexpected inputs (e.g. resolutions deserialized
+    // from external state) so we don't blow up on a missing field.
     const tarball = resolution['tarball'];
+    if (tarball == null) {
+        return { integrity: resolution['integrity'] };
+    }
     // Honor the resolver-supplied flag, with a URL fallback for resolutions
     // that didn't go through the git resolver (e.g. config-dep migrations or
     // legacy lockfiles read by callers that don't enrich the field).
     const gitHosted = resolution.gitHosted === true ||
-        (tarball != null && isGitHostedTarballUrl(tarball));
+        isGitHostedTarballUrl(tarball);
     if (lockfileIncludeTarballUrl) {
         return preservingGitHosted({
             integrity: resolution['integrity'],
@@ -19,20 +25,21 @@ export function toLockfileResolution(pkg, resolution, registry, lockfileIncludeT
     // and registry must always stay in the lockfile, otherwise the package can
     // no longer be re-fetched. This covers local `file:` tarballs and tarballs
     // served by git providers (GitHub, GitLab, Bitbucket).
-    if (tarball != null && (tarball.startsWith('file:') || gitHosted)) {
+    if (tarball.startsWith('file:') || gitHosted) {
         return preservingGitHosted({
             integrity: resolution['integrity'],
             tarball,
         }, gitHosted);
     }
-    if (lockfileIncludeTarballUrl === false) {
-        return {
-            integrity: resolution['integrity'],
-        };
-    }
     // Sometimes packages are hosted under non-standard tarball URLs.
     // For instance, when they are hosted on npm Enterprise. See https://github.com/pnpm/pnpm/issues/867
-    // Or in other weird cases, like https://github.com/pnpm/pnpm/issues/1072
+    // Or in other weird cases, like https://github.com/pnpm/pnpm/issues/1072.
+    // Even when the user explicitly sets `lockfileIncludeTarballUrl: false`, we
+    // must preserve such URLs — otherwise the package cannot be re-fetched on a
+    // frozen-lockfile install (e.g. GitHub Packages tarballs at
+    // `https://npm.pkg.github.com/download/<scope>/<name>/<version>/<hash>`).
+    // `lockfileIncludeTarballUrl` only controls whether URLs that *can* be
+    // derived from name+version+registry are written.
     const expectedTarball = getNpmTarballUrl(pkg.name, pkg.version, { registry });
     const actualTarball = tarball.replaceAll('%2f', '/');
     if (removeProtocol(expectedTarball) !== removeProtocol(actualTarball)) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/lockfile.utils",
-  "version": "1100.0.5",
+  "version": "1100.0.7",
   "description": "Utils for dealing with pnpm-lock.yaml",
   "keywords": [
     "pnpm",
@@ -28,12 +28,12 @@
   "dependencies": {
     "get-npm-tarball-url": "^2.1.0",
     "ramda": "npm:@pnpm/ramda@0.28.1",
+    "@pnpm/deps.path": "1100.0.3",
+    "@pnpm/lockfile.types": "1100.0.5",
     "@pnpm/error": "1100.0.0",
-    "@pnpm/hooks.types": "1100.0.5",
-    "@pnpm/lockfile.types": "1100.0.4",
-    "@pnpm/deps.path": "1100.0.2",
-    "@pnpm/resolving.resolver-base": "1100.1.2",
-    "@pnpm/types": "1101.0.0"
+    "@pnpm/types": "1101.1.0",
+    "@pnpm/resolving.resolver-base": "1100.1.3",
+    "@pnpm/hooks.types": "1100.0.6"
   },
   "devDependencies": {
     "@jest/globals": "30.3.0",
@@ -41,7 +41,7 @@
     "tempy": "3.0.0",
     "write-yaml-file": "^6.0.0",
     "yaml-tag": "1.1.0",
-    "@pnpm/lockfile.utils": "1100.0.5"
+    "@pnpm/lockfile.utils": "1100.0.7"
   },
   "engines": {
     "node": ">=22.13"