Skip to content

[Due for payment 2026-08-07] Investigate workflow job failing on main: typecheck / typecheck #97368

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

  • 📋 Job Name: typecheck / typecheck
  • 🔧 Failure in Workflow: Process new code merged to main
  • 🔗 Triggered by PR: PR Link
  • 👤 PR Author: @neerajbachani
  • 🤝 Merged by: @mountiny
  • 🐛 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.

👀 Please look into the following:

  1. Why the PR caused the job to fail?
  2. Address any underlying issues.

For detailed instructions, check this SO.

🐛 We appreciate your help in squashing this bug!

Activity

  1. mountiny commented on Jul 29, 2026

    @mountiny
    Contributor

    Fixed

  2. changed the title [-]Investigate workflow job failing on main: typecheck / typecheck[/-] [+][Due for payment 2026-08-07] Investigate workflow job failing on main: typecheck / typecheck[/+] on Jul 31, 2026
  3. melvin-bot commented on Jul 31, 2026

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions