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-05-12] Investigate workflow job failing on main: typecheck / typecheck #89471
🐛 Error Message:
failure: Process completed with exit code 2.
failure: Type '{ personalPolicyID: undefined; report: { reportID: string; parentReportID: string; parentReportActionID: string; }; parentReportAction: undefined; action: ReportAction; displayAsGroup: false; shouldDisplayNewMarker: false; index: number; isFirstVisibleReportAction: false; }' is not assignable to type 'IntrinsicAttributes & PureReportActionItemProps'.
failure: Type '{ personalPolicyID: undefined; report: { reportID: string; parentReportID: string; parentReportActionID: string; }; parentReportAction: undefined; action: ReportAction; displayAsGroup: false; shouldDisplayNewMarker: false; index: number; isFirstVisibleReportAction: false; }' is not assignable to type 'IntrinsicAttributes & PureReportActionItemProps'.
⚠️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.
changed the title [-]Investigate workflow job failing on main: typecheck / typecheck[/-][+][Due for payment 2026-05-12] Investigate workflow job failing on main: typecheck / typecheck[/+]on May 5, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.66-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
cristipaval commentedon May 4, 2026
fixing it
[-]Investigate workflow job failing on main: typecheck / typecheck[/-][+][Due for payment 2026-05-12] Investigate workflow job failing on main: typecheck / typecheck[/+]melvin-bot commentedon May 5, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.66-7 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-05-12. 🎊