Category: Vercel and hosting

I put a commit in GitHub, and Vercel shows the old page

Read this guide in Polish

The code in the repository has been corrected and the user still sees the old version of the page.

Where's the problem coming from?

The change could hit another branch, Vercel could have implemented another commit or deploy was not completed. Sometimes a browser or CDN cache occurs.

What to do step by step?

1. Compare SHA commit in GitHub with SHA visible at the production depot Vercel.

2 . Check production branches and repository attached to the project.

3 . If deploy has ERROR status, open build logs and correct the real cause.

4 . If READY, open the exact implementation URL and compare to your own domain.

5 . With the current code, check resource cache, service worker and downloaded API data.

Correction test and important trap

The production deploy indicates the right SHA and in private mode shows the expected change.

Do not clean all caches blindly and do not force new defloys without checking the source commit.