Deployment issue

Help
1

We’re running into a problem where Vercel keeps deploying an old commit (d3ca9c9) instead of our most recent code. Even though we’ve pushed several updates to GitHub, the deployment always reverts back to this outdated version.

We’ve already tried a few things to fix it:

• Updated the vercel.json config

• Removed the vercel.json entirely to let Vercel auto-detect the settings

• Disconnected and reconnected the GitHub repo

• Manually set build commands

Current Status

• The code in our GitHub repo is up to date (we’ve confirmed this, e.g. the “Beta” label is in Navbar.tsx)

• Vercel still insists on deploying the old version

Vercel is stuck deploying from an old commit instead of the latest on the main branch.

What we’ve already tried:

• Disconnecting and reconnecting the GitHub integration

• Changing build settings

• Clearing the cache and redeploying

Why might Vercel be stuck on that specific old commit? Is there a way to force it to pull and deploy from the latest commit on main? Could there be any cached configuration or metadata on their end that needs to be cleared?

2

Hello,

Can you record a screencast and share with us so we can take a closer look? Please also share the link of the project where you are facing this issue.

3

Hi @swarnava

Here’s the link for the project: https://vercel.com/fredrs-projects-ad036d6a/zikzak

We’re experiencing a deployment issue where our React application appears to be serving stale content, specifically a hardcoded timestamp “BETA v3 2025-04-02T12:31:24.660Z” in our navbar, despite multiple deployments with updated code.

Steps Taken:

  1. Made multiple code changes to the Beta label in our Navbar component
  2. Updated Vercel configuration settings
  3. Deleted and recreated the Vercel project
  4. Disabled build optimizations and minification
  5. Added explicit build timestamps and random BUILD_IDs to verify new deployments
  6. Updated cache control headers

Current Behavior:

  • The site consistently shows an old timestamp “BETA v3 2025-04-02T12:31:24.660Z”
  • New deployments don’t reflect code changes
  • The issue persists across different browsers and with cache disabled
  • The issue remains even after recreating the Vercel project

Expected Behavior:

  • The Beta label should show a dynamic timestamp that updates every second
  • Each new deployment should show a different BUILD_ID
  • Changes to the codebase should be reflected in new deployments

Repository Details:

  • Framework: Vite + React
  • Build Command: npm run build
  • Output Directory: dist
  • Main Branch: main

Questions:

  1. Is there a caching layer or build optimization that’s preventing new deployments from being served?
  2. Are there any known issues with Vite builds and static content being cached?
  3. How can we verify that new deployments are actually serving fresh builds?

Thanks,
Fredrik

4

As you can see here: https://www.dropbox.com/scl/fi/4rg4yex8ubm3q7qbktext/Screen-Recording-2025-04-02-at-14.47.17.mov?rlkey=jtywykkmy1zomfqgv972oz6q8&dl=0

I ask cursor to deploy a new obvious change : Changed the navbar background to purple Added a large “:police_car_light: TEST VERSION :police_car_light:” text. Made the logo white (inverted)

It pushes the changes to GitHub and deployed them on Vercel, but when I click the link, the website still appears unchanged.