fix: move minimum-release-age to pnpm-workspace.yaml

[jdalton]

Move pnpm's minimum-release-age from .npmrc to pnpm-workspace.yaml to avoid npm v11+ unknown config warning.

---

Note

Low Risk
Low risk config-only change that just relocates pnpm’s minimum-release-age setting to avoid npm v11+ warnings; behavior should remain equivalent (7-day delay) if tooling reads the new location as expected.

Overview
Moves pnpm’s minimum release age configuration out of .npmrc into pnpm-workspace.yaml via the settings.minimumReleaseAge field (10080 minutes), while keeping npm’s min-release-age=7 (days) in .npmrc.

This prevents npm v11+ from warning about pnpm-only config keys and preserves the intended 7-day delay before installing newly published packages.

^{Reviewed by Cursor Bugbot for commit 1641357. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: minimumReleaseAge nested under invalid settings: key
  • Moved minimumReleaseAge from under the invalid settings: key to the root level of pnpm-workspace.yaml where pnpm expects it, restoring the 7-day supply chain protection.

Or push these changes by commenting:

@cursor push d5ed8d92fd

Preview (d5ed8d92fd)

diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -1,6 +1,5 @@
-settings:
-  # Wait 7 days (10080 minutes) before installing newly published packages.
-  minimumReleaseAge: 10080
+# Wait 7 days (10080 minutes) before installing newly published packages.
+minimumReleaseAge: 10080
 
 packages:
   - packages/*

_{You can send follow-ups to the cloud agent here.}

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 1641357. Configure here.}