Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey 👋,
UPDATE: The team has confirmed that the patch to fix the issue is being rolled out and should be available to everyone soon. Thank you for reporting the issue!
I believe that right now, DigitalOcean App Platform doesn’t provide a way to manually update the Node.js buildpack version. The “latest” tag in the dashboard refers to the version currently supported by DigitalOcean, not necessarily the most recent upstream release.
Since your builds are failing due to the corepack issue with pnpm, one option is to use a Dockerfile instead of relying on the buildpack. This would give you full control over the Node.js version and dependencies, allowing you to install pnpm manually:
https://docs.digitalocean.com/products/app-platform/reference/dockerfile/
Another approach is to define the Node.js version explicitly in your package.json using the engines field, though this won’t necessarily update the buildpack itself though.
If you need an immediate fix, the Dockerfile method is probably your best bet.
It might also be worth reaching out to DigitalOcean support at https://do.co/support to check if there’s a way to request a buildpack update, especially since this is actively breaking builds.
Let me know how it goes!
- Bobby