Three source deployments on the same existing Hobby project passed dependency installation, TypeScript compilation and static page generation, then failed after:
Build Completed in /vercel/output Deploying outputs...
Deployment IDs:
- dpl_2euJEAECTffFB6P2gEEz4HJ95wc9
- dpl_Di3M6fm9ed1S7VXKYmvmTPjQkg9r
- dpl_ApdzP731SDFV87TQgjgEGsgELmb5
The final attempt used the official authenticated Vercel CLI directly. Source contents were unchanged. CLI inspect reports build READY but deployment ERROR with reason: “The deployment failed because of an internal Vercel error.” No fatal build error appears in logs. Next.js 16.3.3, Node 24.x, pnpm 12.3.4. Existing production continues to work.
Vercel Support Agent characterized this as a publication-phase platform failure and directed Hobby users here because private CI/CD tickets are unavailable. Could Vercel staff investigate the publication events or explain what configuration change is needed? We have stopped further retries.
No credentials, environment variable values, source code or customer data are included.