#builds

Muhehee Bumping this for the dev team's visibility. Since support confirmed this is an infrastructure bug but Hobby users can't open tickets, we really need an engineer to check this out. Our staging environment is still blocked.

Pauline P. Narvas Hey, Brightpixels! Welcome to the Vercel Community 👋 For anyone else reading this, this is about the live property from the Vercel REST API, docs here: vercel.com/docs/rest-api/projects/retrieve-a-list-of-projects From my understanding, the live property appears to be an internal state that tracks whether your production deployment is actively serving traffic, which is separate from the paused state. When a project is paused, both paused: true and live: false are set. It looks like the unpause endpoint might not be properly restoring the live state in your case. To resolve this: Try triggering

Ryu Hi Devansh, If those Sentry events cluster around deploy times, I’d treat this as version skew first. With dynamic(() => import(...), { ssr: false }), the browser may not request that CSS/JS chunk until later. If the user loaded HTML/JS from an older deployment, then a new production deployment goes live, that old client can later try to fetch a chunk URL that no longer exists on the deployment it is being routed to. That usually shows up as: Loading CSS chunk failed /_next/static/css/<hash>.css A good way to confirm is to check the failed asset request in Sentry or browser devtools: status: 4

sprucepad The title seems to have been changed, it shows “25m / 0s” on the dashboard. It also seems to be completely ignored, as I just deployed something just fine.

sprucepad It seems to have disappeared, so maybe Vercel’s adding build time limits and it was glitched out.

Aconfusedprogrammer I had this issue too. I still have it, but I can still deploy just fine.

Ryu Hi Sbullocks, Since static assets work but every function hangs until timeout, I’d separate “Vercel can route to a function” from “your new runtime code is waiting forever.” First, deploy one tiny endpoint that does not import anything shared from the app: // app/api/ping/route.ts export const dynamic = "force-dynamic" export async function GET() { return Response.json({ ok: true, time: Date.now() }) } If that works, the platform/function routing is fine and I’d look at the changes from the rate-limiting commit: middleware, shared auth helpers, Redis/KV/database clients, external fetches, or e

Craiguito This is usually tied to the exact author on the commit Vercel is deploying, not just the email on your GitHub profile. Check the commit that failed: git log -1 --format='%an <%ae>' Then compare that email to the email GitHub shows for that commit on github.com. If the commit uses an old email, a private noreply email that is not tied to your account, or a bot author, Vercel can treat it as an outside collaborator on Hobby. The fix is usually to set git author email locally, make a new commit, and push that: git config user.name "Your GitHub name" git config user.email "your_verified_github_ema

Ryu Hi Abhi, For Hobby projects connected to a private GitHub repo, Vercel needs to verify that the commit author is the Hobby team owner. So I’d check the actual commit author, not only the email on your GitHub/Vercel profile. Run this on the commit that failed: git log -1 --format="%an <%ae>" Then open that commit on GitHub and confirm GitHub associates it with your GitHub user. If GitHub shows it as unverified, unknown, a bot, or a different account, Vercel may treat it like an outside collaborator even if you are the only person using the repo. If the email is wrong, set it locally and push a

Tianen Pang check this one github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix

ADALIGO The error comes from tooling mismatch not from you Luknuts56, just downgrade ESLint and you’re good 👍

Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your loading.tsx file. Your package.json has: "eslint": "10.0.3", "eslint-config-next": "^16.1.7" and the stack trace is failing inside eslint-plugin-react while loading the react/display-name rule. There’s an open Next.js issue for this same ESLint 10 error: github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: pnpm add -D eslint@^9 eslint-config-next@latest pnpm lint If it still keeps ESLint 10 because of the lockfile, do a clean install: rm -rf node_modules pnpm-lo

Josh To add, I have a hobby account on Vercel and a Pro account. I was trying to add the personal GitHub to the hobby account and keep the work GitHub on the pro account. Maybe I really only have one account on Vercel (I saw that only 1 GitHub account may be used per Vercel account – the UI is confusing here because then why does it say Add Account)?

Amy Egan Yes, you can connect one GitHub account to a single Vercel account. That is the expected behavior. vercel.com/kb/guide/connecting-teams-with-personal-git-accounts

ADTC FWIW, you can set up GitHub Actions to indirectly deploy your projects into Vercel without connecting your GitHub account. See gist.github.com/ADTC/63ce24ca5a6c306f05d75ad2d6975e93

Pauline P. Narvas Thank you for your contribution, Michele! Welcome to the Vercel Community 🙂 I've passed this onto the CICD team to review!

Michele Bertoli Gentle nudge on this one It's a 2-line change that brings @vercel/react-router in line with how Next.js, SvelteKit, and Qwik already set vdpl and it unblocks Skew Protection for deep URLs Happy to add a changeset or any tweaks that'd help, just let me know