chore(deps): update pnpm to v11.8.0 [security]

Author: renovate[bot]

package.json

@@ -55,7 +55,7 @@
         "typescript": "^6.0.0",
         "typescript-eslint": "^8.58.0"
     },
-    "packageManager": "pnpm@11.5.1",
+    "packageManager": "pnpm@11.8.0",
     "devEngines": {
         "packageManager": {
             "name": "pnpm",

pnpm-workspace.yaml

@@ -10,12 +10,14 @@
 # we publish them ourselves.
 minimumReleaseAge: 1440
 minimumReleaseAgeExclude:
-    - '@apify/*'
-    - '@crawlee/*'
-    - 'apify-client'
-    - 'apify'
-    - 'crawlee'
-    - 'got-scraping'
+  - '@apify/*'
+  - '@crawlee/*'
+  - 'apify-client'
+  - 'apify'
+  - 'crawlee'
+  - 'got-scraping'
+  # Renovate security update: pnpm@11.8.0
+  - pnpm@11.8.0
 
 # Lets unknown build-requesting deps fall back to a warning instead of erroring
 # out, so a new build-requesting dev dep doesn't break the install before it
@@ -26,13 +28,13 @@ strictDepBuilds: false
 # Chrome binary; `unrs-resolver` builds native bindings for the eslint resolver
 # used by @apify/eslint-config.
 allowBuilds:
-    puppeteer: true
-    unrs-resolver: true
+  puppeteer: true
+  unrs-resolver: true
 
 # Force @puppeteer/browsers v3+ everywhere. Older versions (puppeteer 24.x pulls
 # 2.13.x transitively) use an extract-zip flow that freezes mid-extraction on
 # Node 24.16+, leaving ~/.cache/puppeteer half-populated and breaking subsequent
 # template installs. Mirrors the fix in apify/crawlee#3703.
 # Refs: nodejs/node#63495, puppeteer/puppeteer#14957.
 overrides:
-    '@puppeteer/browsers': ^3.0.4
+  '@puppeteer/browsers': ^3.0.4