Replies: 5 comments 6 replies
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the deployment is being created successfully, but it's failing while GitHub Pages is trying to publish it. The punycode deprecation warning is unrelated and shouldn't be the cause. Have you tried rerunning the workflow after a few minutes? Also, is this happening only in this repository or across multiple repositories? If it's affecting multiple repos, it could be a temporary GitHub Pages issue even if the status page isn't reporting anything. If you can share the workflow run link or your Pages configuration, it might help narrow it down. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also getting failed github page deploys, feels like the service is degraded but the status page isn't reflecting that... Run actions/deploy-pages@v5 (node:2306) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) Fetching artifact metadata for "github-pages" in this workflow run Found 1 artifact(s) Creating Pages deployment with payload: { "artifact_id": 8070542448, "pages_build_version": "6acbd85d37a2e9390337fe45ba00fe0bd30060c7", "oidc_token": "***" } Created deployment for 6acbd85d37a2e9390337fe45ba00fe0bd30060c7, ID: 6acbd85d37a2e9390337fe45ba00fe0bd30060c7 Getting Pages deployment status... Error: Deployment failed, try again later. |
Beta Was this translation helpful? Give feedback.
-
|
The "Deployment failed" error during the status check is a common, transient issue with GitHub Pages infrastructure. It is almost certainly not caused by your code. Troubleshooting Steps
Next StepsIf this persists beyond 24 hours, contact GitHub Support to clear a "wedged" deployment status on your account. Are you seeing these failures consistently across all branches, or just on the main branch? |
Beta Was this translation helpful? Give feedback.
-
|
The issue is resolved. The fix seems to be something my AI did. here are some notes from my Claude Code session: What worked The wedged workflow runs couldn't be canceled, force-canceled, or deleted (409 / 403 responses). But GitHub Pages has a separate legacy build endpoint — POST Summary of what unblocked it
Handy commands to save If this happens again on a legacy-Pages site: check statusgh api /repos/OWNER/REPO/pages force a rebuild bypassing stuck workflowsgh api -X POST /repos/OWNER/REPO/pages/builds |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
I've been getting this all morning when trying to deploy my latest commits:
The GitHub status page notes no issues, but I haven't been able to successfully deploy anything on TrialProtocols.com (https://github.com/mroswell/trialprotocols) for at least an hour.
Beta Was this translation helpful? Give feedback.
All reactions