Robustly discover packages with @manypkg

fixtures/pnpm/multi-lockfile/.npmrc

@@ -0,0 +1,13 @@
+# npm / pnpm settings here
+
+# as a library, we want to make sure we explicitly handle peers,
+# and not rely on hidden behavior of package-managers.
+auto-install-peers=false
+
+# we never want to use packages from the registry over what's in the workspace
+prefer-workspaces-packages=true
+
+# default is true, we do this to try to have more isolation
+# since we test with incompatible sets of TS types.
+shared-workspace-lockfile=false
+

fixtures/pnpm/multi-lockfile/package.json

@@ -0,0 +1,3 @@
+{
+  "private": true
+}

fixtures/pnpm/multi-lockfile/packages/a/package.json

@@ -0,0 +1,4 @@
+{
+  "name": "a",
+  "version": "0.0.1"
+}

fixtures/pnpm/multi-lockfile/packages/b/package.json

@@ -0,0 +1,4 @@
+{
+  "name": "b",
+  "version": "0.0.1"
+}

fixtures/pnpm/multi-lockfile/packages/c/package.json

@@ -0,0 +1,5 @@
+{
+  "name": "c",
+  "version": "0.0.1"
+}
+

fixtures/pnpm/multi-lockfile/pnpm-workspace.yaml

@@ -0,0 +1,2 @@
+packages:
+  - './packages/*'

fixtures/pnpm/single-package/package.json

@@ -0,0 +1,4 @@
+{
+  "name": "foo-package",
+  "version": "0.0.1"
+}

fixtures/pnpm/single-package/pnpm-workspace.yaml

@@ -0,0 +1,2 @@
+packages:
+  - '.'

package.json

@@ -18,7 +18,8 @@
     "test": "vitest"
   },
   "dependencies": {
-    "@ef4/lerna-changelog": "^2.0.0",
+    "@ef4/lerna-changelog": "^2.1.0",
+    "@manypkg/get-packages": "^2.2.0",
     "@npmcli/package-json": "^5.0.0",
     "@octokit/rest": "^19.0.8",
     "@types/fs-extra": "^9.0.12",