From 2a3db08b8d1cc6800630273e9d5cb84d05899080 Mon Sep 17 00:00:00 2001
From: Sarah Fortune <153992+sjf@users.noreply.github.com>
Date: Wed, 6 May 2026 16:33:34 -0700
Subject: [PATCH] fix(workspace): add packages field so pnpm prepare succeeds

pnpm-workspace.yaml carried only allowBuilds, with no packages field.
Recent pnpm rejects this with ERR_PNPM_INVALID_WORKSPACE_CONFIGURATION
("packages field missing or empty") during the prepare step it runs
inside any consumer that pulls @openclaw/fs-safe from a github tarball,
breaking installs in downstream repos that pin a commit (e.g. openclaw).

Adding packages: [] keeps the file a valid (empty) workspace root while
preserving the allowBuilds: { esbuild: true } directive. Verified by
extracting the working tree to a clean directory and running
pnpm install -- which now completes without error.
---
 pnpm-workspace.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index 5ed0b5a..2137e88 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -1,2 +1,4 @@
+packages: []
+
 allowBuilds:
   esbuild: true