Comments (5)
Unfortunately, given the types of errors that cause this blanket "deployment failed" scenario, we tend to not want to expose them since they're related to some more sensitive internal bits. 😓
Anyway, good news: the problem was identified, corrected, deployed, and Pages should be back to fully operational status now. 🚀
from deploy-pages.
Thank you for the reporting, and apologies for the unhelpful error message! 🙇
We are aware of it and investigating. You can check on the current incident status at https://www.githubstatus.com/incidents/hzd6d6xhjpl6
If you need to deploy urgently, the only workaround at the moment would be to revert to using actions/upload-pages-artifact@v2
and actions/deploy-pages@v3
.
from deploy-pages.
"Me too"
It was working on the 22nd of December, has been failing just now, including deploying the exact same code that was deployed successfully on the 22nd
from deploy-pages.
Explicitly reverting to v4.0.1 or v4.0.0 (instead of simply v4) also does not help
from deploy-pages.
Hi James, I was actually just in the middle of typing a comment including that link.
As for making the error more useful, maybe the raw error could also be included in core.error
in addition to the error messages so we can get more insight into why our actions fail?
from deploy-pages.
Related Issues (20)
- Upgrade `@octokit/request.js` to `v8.1.5` after updating to run on `node20`
- Unable to deploy, task marked as completed but the artifact is not uploaded HOT 2
- Add rough error handler for Octokit response parsing failures to `1.x` and `2.x` release
- HttpError: Invalid environment node id HOT 6
- Is there a way to use this in the composite action? HOT 3
- [QUESTION] Is it possible to deploy a single file without losing existent files? HOT 1
- Actions fail after update actions/deploy-pages to v4 and actions/upload-pages-artifact to v3 HOT 17
- Failing to fetch artifact metadata since 4.0.0 HOT 8
- Bump to V4 broke the deploy step HOT 9
- Remove requirement for `actions: read` permission HOT 1
- Page Deployment Failing Periodically with Timeouts since Upgrade to v4 HOT 1
- Getting "Fetching artifact metadata failed." HOT 3
- Confusing error when trying to deploy Rust docs HOT 6
- CNAME file doesn't work to set custom domain
- Error: No artifacts named "github-pages" were found for this workflow run. HOT 5
- Deploy to another repository HOT 2
- GitHub Enterprise Server 3.11.5 compatibility HOT 6
- Deployment protection rules seem to be ignored HOT 1
- 502 error on github enterprise HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from deploy-pages.