-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-08-07] Investigate workflow job failing on main: typecheck / typecheck #46285
Comments
Fixed! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.14-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-08-07. 🎊 |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@Gonals Huh... This is 4 days overdue. Who can take care of this? |
@Gonals 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@Gonals 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@Gonals 12 days overdue now... This issue's end is nigh! |
This issue has not been updated in over 14 days. @Gonals eroding to Weekly issue. |
🚨 Failure Summary 🚨:
warning: The following actions uses Node.js version which is deprecated and will be forced to run on node20: nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
failure: Argument of type '{ readonly route: "onboarding"; readonly getRoute: (backTo?: string) => "onboarding" |
onboarding?backTo=${string}
|onboarding&backTo=${string}
; }' is not assignable to parameter of type 'Route | undefined'.failure: Process completed with exit code 2.
🛠️ A recent merge appears to have caused a failure in the job named typecheck / typecheck.
This issue has been automatically created and labeled with
Workflow Failure
for investigation.👀 Please look into the following:
🐛 We appreciate your help in squashing this bug!
The text was updated successfully, but these errors were encountered: