GitHub Pages blocks new deployments on a completed version after publication reset

[morgan254917]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Repository: https://github.com/morgan254917/bidbell-site
Account: morgan254917
Website: https://getbidbell.com

Please clear a stale GitHub Pages deployment lock without changing our domain, HTTPS settings or live content. The site is currently available on the last successful version, but every newer publication is blocked.

GitHub reports:
Deployment request failed due to in progress deployment. Please cancel 3b0729ab0a6fa9ad930180a6bf152d5842f172c4 first or wait for it to complete.

That version's deployment job completed successfully:
https://github.com/morgan254917/bidbell-site/actions/runs/41289009026
Its deploy log says "Reported success!". Rerunning that exact last-good artifact also succeeds and restored the site after a temporary unpublish.

Newer versions continue to fail, including the current checked main commit 7d9b62018d7aecb604f4bd16d9463ba27fb78053:
https://github.com/morgan254917/bidbell-site/actions/runs/41291272992
The build and all 18 website plus 4 checkout checks pass. Failure occurs only when creating the Pages deployment.

Recovery attempts already completed:

• Waited for the earlier workflow to finish and retried the failed deployment job.
• Requested a fresh build through the documented Pages builds endpoint.
• Queried the stale Pages deployment status: HTTP 404.
• Canceled that exact Pages version through the documented endpoint: HTTP 400, "Unable to cancel deployment ... as it's finished."
• Preserved deployment-history record 7470603087, marked it inactive, then removed that one record with the owner's explicit approval. The lock persisted.
• Switched from legacy branch publication to the documented official Actions workflow, with sequential publication and the same github-pages environment. The lock persisted.
• With the owner's separate approval, temporarily unpublished the site and redeployed. Newer versions still failed; rerunning the last-good version restored availability.

Please inspect and clear the backend pointer/lease for the completed 3b0729ab0a6fa9ad930180a6bf152d5842f172c4 Pages version, or provide a documented recovery that preserves the live site. We have not deleted the repository, its Git history, source files or domain settings. HTTPS is still enforced.

This report contains public repository and deployment identifiers only. No customer data, credentials or payment details are included.

[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. ⭐