GitHub Pages serves cached 404 for deployed paths on user site maksimshdev.github.io — request edge cache purge + clearing of stuck deployment

[maksimshdev]

🏷️ Discussion Type

Bug

Body

Repository: github.com/maksimshdev/maksimshdev.github.io (public user Pages site)

Affected URLs — both return HTTP 404:

• https://maksimshdev.github.io/easypeasyenglish/privacy/
• https://maksimshdev.github.io/easypeasyenglish/delete-account/

SUMMARY
GitHub Pages is returning 404 for paths that are correctly deployed. Settings → Pages reports the site as live and last deployed successfully ~1 hour ago via the "Deploy static content to Pages" GitHub Actions workflow, yet these valid paths 404. This has persisted for several days across multiple deploys and every self-service fix.

VERIFIED FACTS (already confirmed on my side — please do not ask me to re-check these):

1. Pages Source = GitHub Actions. Settings → Pages shows "Your site is live at https://maksimshdev.github.io/", last deployed ~1h ago by the "Deploy static content to Pages" workflow; the latest run is green.
2. The workflow is the unmodified GitHub "Static HTML" starter: actions/upload-pages-artifact@v3 with path: '.' (entire repository uploaded), then actions/deploy-pages@v5.
3. The files exist at the exact requested paths on the default branch (main):
   • easypeasyenglish/privacy/index.html
   • easypeasyenglish/delete-account/index.html
     Raw returns HTTP 200, e.g.:
     https://raw.githubusercontent.com/maksimshdev/maksimshdev.github.io/main/easypeasyenglish/privacy/index.html
4. .nojekyll is present at the repository root; there is no _config.yml and no custom 404.html. Jekyll processing is disabled.
5. The Pages artifact produced by the green runs contains both files.
6. Already tried, no effect: re-running the deploy workflow; "Re-run all jobs"; Unpublish + republish the site; switching Source from "Deploy from a branch" to "GitHub Actions"; adding .nojekyll; cache-busting query strings; testing from multiple devices, browsers, incognito, and a separate mobile network.
7. Legacy "pages build and deployment" runs (Feature request: support jumping to lines in files #5, #6, Allow For Multiple Answers To Be Marked as Answer #9) are stuck in "Queued" and cannot be cancelled from the UI ("Failed to cancel"). This previously caused newer runs (Allow for custom notifications for only when a discussion is answered #8, More defined voting system #10) to be auto-cancelled with: "Canceling since a higher priority waiting request ... @ main exists."

DIAGNOSIS
The deployment is green and the artifact is correct, but the edge is serving a cached 404 for these paths — consistent with a poisoned negative cache and/or the stuck legacy deployment queue blocking publication of the current artifact.

WHAT I NEED YOU TO DO

1. Force-purge the GitHub Pages edge/CDN cache for maksimshdev.github.io — specifically /easypeasyenglish/privacy/ and /easypeasyenglish/delete-account/ (and the apex).
2. Clear the stuck "Queued" legacy "pages build and deployment" runs (Feature request: support jumping to lines in files #5, #6, Allow For Multiple Answers To Be Marked as Answer #9) that cannot be cancelled from the UI.
3. Confirm which deployment (commit SHA + run ID) is currently being served at the edge.

BUSINESS IMPACT / URGENCY
This Pages site hosts the Privacy Policy and account-deletion pages that are legally required to publish my app on Google Play. This 404 is the single blocker preventing store submission and the start of a mandatory 14-consecutive-day closed-testing window. Every day it stays broken delays the release. I previously emailed about this and received no response — please assign a ticket number and engage an engineer rather than a templated reply.

Contact email: max.shalot@gmail.com

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐