Reference upstream issue in sideEffectsCache workaround comment

Author: Nils-Kolvenbach

pnpm-workspace.yaml

@@ -20,11 +20,12 @@ allowBuilds:
   # so its postinstall build is redundant. Same reasoning as in Core.
   esbuild: false
 # Do not reuse pnpm's cache of postinstall (side effect) output. Since pnpm 8.7
-# the content addressable store keeps such files as plain copies, not symlinks
-# (pnpm/pnpm#7691). dugite's postinstall lays down git, whose git-core is ~145
-# symlinks to one binary. Restoring that from a warm store (the CI pnpm cache)
-# flattens them into 145 full copies, which doubled the packaged macOS app.
-# With this off dugite re-extracts git each install, so the symlinks survive.
+# the content addressable store keeps such files as plain copies, not symlinks.
+# dugite's postinstall lays down git, whose git-core is ~145 symlinks to one
+# binary. Restoring that from a warm store (the CI pnpm cache) flattens them
+# into 145 full copies, which doubled the packaged macOS app. With this off
+# dugite re-extracts git each install, so the symlinks survive.
+# Reported as pnpm/pnpm#12859 (see also #7691). Remove once that is fixed.
 sideEffectsCache: false
 # Temporary: pnpm's default minimumReleaseAge policy (about one day) rejects
 # freshly published packages on a clean install, which is what CI runs.