Build is not using the latest commit from GitHub repo

Hello,

My Vercel project is not deploying the latest version of my files from the connected GitHub repository. The build continues to fail with an error for a file that no longer exists in the latest commit.

  • Project: electrical-safety-education
  • GitHub Repo: https://github.com/Sakurayuki89/electrical-safety-education
  • Problem: The build fails with the error “Cannot find module ‘./config’” or “Function Runtimes must have a valid version”, even though the code on the main-fix branch has already fixed these issues. The deployment log shows Vercel is building from an old commit, not the latest one.

Troubleshooting I have already tried:

  • Redeploying without the build cache.
  • Deleting and recreating the entire Vercel project.
  • Pushing the code to a new branch (main-fix) and trying to deploy from there.

Even after all these steps, Vercel does not seem to pull the latest version of the code for a new deployment. How can I force Vercel to sync with the latest commit from my GitHub repository?

Thank you.

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

You can also use v0 to narrow down the possibilities.

Following

In my case deployment page shows the correct commit
but the deploy is failing on linting errors in files which are not present in github in that commit/branch and which are not shown in the vercel file explorer in the source tab for the deployment

Also cannot figure out how to force the build to use the actual code from the latest commit.
Setting VERCEL_FORCE_NO_BUILD_CACHE=1 showed no impact.
Support: see https://vercel.com/carta-consulting/pundit-factory/BQN8HhWRfoLkgrjAt37TdecFc5B8 for an example deployment

next troubleshooting seems to be to de-link / re-link the github for the project but would rather not do that if this is really a build/linter caching error in the back end…

edit: we also tried adding .eslintignore entries and lint directives in package.json without effect.
its like the linter is on autopilot.