Vercel keeps serving old version after deploy (Astro) Urgent help

Help
, , , ,
1

Hi, I have an Astro project where deployments complete normally (status: Ready), but the live site keeps showing old content.

Changes I hardcode directly inside components do NOT update on the production URL.
I already tried:

– Clearing build cache
– Purging CDN cache
– Redeploying several times
– Testing in incognito and other browsers
– Changing output folder
– Recreating the project from zero

Local build is correct, but Vercel keeps serving stale assets in production.

It seems like an edge-cache issue or something stuck at platform level.

Is there any known cause for this?

What else can I try to force Vercel to serve the new build?

Thanks,

4

Do you have a link we can look at?

Do you have any caching headers at all? Maybe in your vercel.json?

5

Hi Pauline, thanks for your reply!

I finally found the issue.

The problem was that the .vercel/output folder had been accidentally committed to the repository, so Vercel was always using those prebuilt artifacts instead of running a fresh build from the current code.

Fix:

  • I deleted the entire .vercel/ folder locally

  • Added .vercel/ to .gitignore

  • Pushed a clean commit

  • Cleared the build cache on Vercel and redeployed

After that, Vercel stopped serving the stale version and everything worked correctly.

Leaving this here in case it helps someone else :slight_smile: