Vercel Not Deploying Latest GitHub Updates — Stuck on Old Repo? - Help

Hi everyone,

We’ve encountered a frustrating issue with Vercel, and I’m hoping someone can shed light on it or suggest a solution.

This is now the 8th time we’ve had to delete the entire deployment just to get Vercel to recognize updates from our GitHub repo. Even for small changes, Vercel keeps deploying from an old repository—one that doesn’t even exist anymore in our GitHub account.

Here’s what we’ve tried:

Confirmed that the correct repo is connected in Vercel settings
Verified GitHub access permissions for Vercel
Pushed clean commits to the correct branch
Manually triggered redeploys from the dashboard

Despite all this, the "Source" in the deployment logs still shows outdated files from the previous repo. It’s like Vercel is caching or stuck on a ghost repo.

Has anyone else experienced this? Is there a way to force Vercel to fully reset its source mapping without deleting the entire project every time? I don’t want to keep deleting an ENTIRE project just to get a “Pricing” change updated. Whenever I push to GitHub it’s there within 30 seconds or a minute. Vercel on automatic should be able to “SEE” the change and run an update, but it doesn’t, and when we push the redeploy button, it’s deploying an old starter repo.

Any help or insight would be hugely appreciated!

Thanks in advance

Did you know there's another category dedicated to #v0 topics? A human should be here soon to help, but the answer may already be available even faster in one of these other posts.

Our docs are a great place to start.

https://vercel.com/docs/v0

We also have a walkthrough to help guide your workflow.

https://community.vercel.com/t/become-a-v0-expert/5981

And these recordings can give you a look at v0 features and strategies in action shown by our Community:

https://community.vercel.com/tags/c/events/42/v0

Sorry, Vercel, we’re packing up. We’ve decided to move to a host that actually shows up when support is needed, and hey, we’ll save money while we’re at it. The backlog of unresolved issues in your community speaks volumes. It feels like your paid users are expected to crowdsource solutions while your team watches from the sidelines. If your business model depends on customers doing the heavy lifting, maybe it’s time to rethink who’s really earning that paycheck. Adios!

Try to push your new version of code in a new branch of the repo you have connected to the deployment in vercel , after pushing the code in new branch . Visit your project in vercel and go to overview section at the bottom you would see active branches and there would be your new branch where you pushed your new code , click on three dots then View all Deployments , find your branch and click on three dots and then promote deployment after that you would figure out.