You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-08-07] Investigate workflow job failing on main: typecheck / typecheck #97368
🐛 Error Message:
warning: [git-mirror] Skipping cache commit: Found 2 failed/cancelled steps
warning: [git-mirror] - Step: unknown (failed)
warning: Skipping sticky disk commit due to previous step failures
warning: - Step: unknown (failed)
warning: Found 2 failed/cancelled steps in previous workflow steps
warning: Skipping sticky disk commit due to previous step failures
warning: - Step: unknown (failed)
warning: Found 2 failed/cancelled steps in previous workflow steps
failure: Process completed with exit code 2.
failure: Type 'string' is not assignable to type 'SearchKey'.
⚠️Action Required⚠️:
🛠️ 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.46-10 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 2026-08-07. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
mountiny commentedon Jul 29, 2026
Fixed
[-]Investigate workflow job failing on main: typecheck / typecheck[/-][+][Due for payment 2026-08-07] Investigate workflow job failing on main: typecheck / typecheck[/+]melvin-bot commentedon Jul 31, 2026
@mountiny
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.46-10 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 2026-08-07. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]