-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Main build is failing after merging VSCode workspace PR 3929 #4099
Labels
🚒 incident
Production incident
Comments
5 tasks
This issue persists intermittently, unrelated to the original trigger Latest one here https://github.com/winglang/wing/actions/runs/6102723404/job/16561847776 |
@MarkMcCulloh maybe we should try unpinning the |
This was referenced Sep 7, 2023
mergify bot
pushed a commit
that referenced
this issue
Sep 7, 2023
Fixes #4099 Waiting for nodejs/node#49497 to be released *By submitting this pull request, I confirm that my contribution is made under the terms of the [Wing Cloud Contribution License](https://github.com/winglang/wing/blob/main/CONTRIBUTION_LICENSE.md)*.
Congrats! 🚀 This was released in Wing 0.29.6. |
mergify bot
pushed a commit
that referenced
this issue
Sep 14, 2023
This reverts commit 6344bc0. I was reverted in #4100 due to #4099 - a hangar test failing on node20. Tried to reproduce it locally without success. So, trying it in CI again. ## Checklist - [ ] Title matches [Winglang's style guide](https://www.winglang.io/contributing/start-here/pull_requests#how-are-pull-request-titles-formatted) - [ ] Description explains motivation and solution - [ ] Tests added (always) - [ ] Docs updated (only required for features) - [ ] Added `pr/e2e-full` label if this feature requires end-to-end testing *By submitting this pull request, I confirm that my contribution is made under the terms of the [Wing Cloud Contribution License](https://github.com/winglang/wing/blob/main/CONTRIBUTION_LICENSE.md)*.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Incident description
After merging the following PR to
main
the build failed:Failed github action
We're currently looking into it and will revert if we can't find a fix soon.
Is there a workaround?
No response
Incident Response Checklist
The text was updated successfully, but these errors were encountered: