Add packages to pnpm-workspace.yaml to include root package

[marcalexiei]

• Follow up of migrate to pnpm #112 (comment)

Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 4 cores, 8 GB
Cloning github.com/changesets/bot (Branch: master, Commit: ea5e300)
Cloning completed: 259.000ms
Skipping build cache since Package Manager changed from "yarn" to "pnpm"
Running "vercel build"
Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x
Using pnpm@9.x based on project creation date
To use pnpm@10.x, manually opt in using corepack (https://vercel.com/docs/deployments/configure-a-build#corepack)
Installing dependencies...
 ERROR  packages field missing or empty
For help, run: pnpm help install
Error: Command "pnpm install" exited with 1

---

• I updated the packageManager field, removing the hash to keep the same format that was previously used with yarn.
  

  bot/package.json

  Line 49 in af23c7e

  "packageManager": "yarn@1.22.22"

  
  Not needed, adding repo root to pnpm-workspace.yaml#packages solved the issue
• Since the error mentions packages field missing or empty, I added a packages entry pointing to the repository root in pnpm-workspace.yaml.

Additional changes to try if the deployment still fails

• Clear any existing build cache that may still contain Yarn artifacts and interfere with the new pnpm-based build.
• The Vercel documentation also mentions enabling Corepack explicitly by setting: ENABLE_EXPERIMENTAL_COREPACK=1
  Reference: https://vercel.com/docs/builds/configure-a-build#corepack

[vercel]

@marcalexiei is attempting to deploy a commit to the Changesets Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
changesets-bot	Ready	Preview, Comment	May 20, 2026 6:55am

[Andarist]

Hm, the preview deployment got built but something looks off cause I see this in the logs:

index.ts(101,53): error TS7006: Parameter 'commentsResponse' implicitly has an 'any' type.
index.ts(104,8): error TS7006: Parameter 'comment' implicitly has an 'any' type.
index.ts(114,29): error TS7006: Parameter 'filesResponse' implicitly has an 'any' type.
index.ts(116,8): error TS7006: Parameter 'file' implicitly has an 'any' type.
index.ts(161,51): error TS7006: Parameter 'filesResponse' implicitly has an 'any' type.
index.ts(162,39): error TS7031: Binding element 'filename' implicitly has an 'any' type.
index.ts(172,171): error TS2339: Property 'message' does not exist on type 'ValidationError'.
get-changed-packages.ts(67,16): error TS2339: Property 'json' does not exist on type 'Response'.
get-changed-packages.ts(78,16): error TS2339: Property 'text' does not exist on type 'Response'.

I'm not sure if this is a new issue or if that was present with Yarn

[marcalexiei]

get-changed-packages.ts(67,16): error TS2339: Property 'json' does not exist on type 'Response'.
get-changed-packages.ts(78,16): error TS2339: Property 'text' does not exist on type 'Response'.

Those lines make me think there’s a mismatch in the loaded types.
Hopefully, explicitly adding them to the tsconfig will solve the issue.

The errors in index seem to come from probot’s types, which also rely on @types/node, so hopefully those are fixed as well now.

[Andarist]

I still see those in the logs:

index.ts(101,53): error TS7006: Parameter 'commentsResponse' implicitly has an 'any' type.
index.ts(104,8): error TS7006: Parameter 'comment' implicitly has an 'any' type.
index.ts(114,29): error TS7006: Parameter 'filesResponse' implicitly has an 'any' type.
index.ts(116,8): error TS7006: Parameter 'file' implicitly has an 'any' type.

I'll investigate this further tomorrow unless you know what the fix for this should be

[Andarist]

It still errors with the same type errors but I have found the culprit: vercel/vercel#16370

I think it's fine to ship this because it shouldn't quite affect the deployed code. We should replace the implicit build script with rolldown, like here: changesets/action#621 . We gotta be careful about aligning the output /api with the source files and the rolldown's entry points.