Here are my steps for clues to the origin of the problem:
- Edit
index.html
conspicuously. - Commit and push to github.
- Wait for the deploy
645089edf4904f000893daff
to complete building on netlify. - Download the build using the image button to the right of the label
Production: main@81a27fd
. - Verify that the
index.html
in the downloaded “zip with deployed files” is identical to the one pushed to github. - Click
Open Production Deploy
but the page source is the stale index.html. curl -i [https://main--claritygpt.netlify.app/
](https://main--claritygpt.netlify.app/`) returns the stale index.html with these headers:
HTTP/2 200
accept-ranges: bytes
age: 49090
cache-control: public, max-age=0, must-revalidate
content-type: text/html; charset=UTF-8
date: Tue, 02 May 2023 03:01:32 GMT
etag: "5f218611fa909600972378eacd2d393b-ssl"
server: Netlify
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-nf-request-id: 01GZENB19FMM9Y64SS3XTEN2Z3
content-length: 1337
everything at Netlify is working as designed. It may not be working in the way you expected but it is working correctly.
My point is that the branch subdomain of[main--claritygpt.netlify.app](http://main--claritygpt.netlify.app)
is locked to that April 27th deploy because auto-publishing of that branch is locked.
It is unexpected that the branch subdomain can be locked, perhaps because I’m using it to preview the deploy. There is no indication it is locked in the UI, and no Option to enable auto-publishing.
Related: https://answers.netlify.com/t/create-a-branch-deployment-of-my-production-branch/91434