[Due for payment 2026-06-11] [Due for payment 2026-06-10] App main CI is red — typecheck/ESLint fail with 'Cannot find name allPolicies'

[blimpich]

Problem

Every PR that pulls in the latest main fails CI on two checks — typecheck and ESLint check — so nothing can merge and the backend deploy is blocked. The failures are identical across unrelated PRs (e.g. #84791, #92429), confirming the breakage is on main itself rather than in any one PR.

The shared error:

src/components/Search/SearchFiltersParticipantsSelector.tsx(72,81):
error TS2304: Cannot find name 'allPolicies'.

with the matching @typescript-eslint/no-unsafe-argument ESLint error at the same 72:81 location.

Reproduction Steps

These apply to CI on main (and any branch with main merged in).

1. Branch from latest main.
2. Run npm run typecheck (or npm run lint).

Expected Behavior: typecheck and ESLint pass.

Actual Behavior: both fail with Cannot find name 'allPolicies' / no-unsafe-argument at src/components/Search/SearchFiltersParticipantsSelector.tsx:72:81.

Solution

PR #92045 ("Stop scroll jump on search filter participant selection") removed the Onyx binding const [allPolicies] = useOnyx(ONYXKEYS.COLLECTION.POLICY); from SearchFiltersParticipantsSelector.tsx, but left the usage of allPolicies at line 72:

const expensifyTeamExclusions = getExpensifyTeamExclusions(personalDetails, allPolicies, currentUserEmail);

Re-add the allPolicies useOnyx binding alongside the component's other hooks. useOnyx and ONYXKEYS are already imported, so no other changes are needed.

Extra context

The sibling component src/components/Search/FilterComponents/UserSelector.tsx still has the correct pattern (const [policies] = useOnyx(ONYXKEYS.COLLECTION.POLICY); passed into the same getExpensifyTeamExclusions util), confirming the intended shape.

The ESLint no-unsafe-argument error is a downstream symptom: with allPolicies unresolved, TypeScript types it as any/error, which makes it an "unsafe argument". Restoring the binding fixes both errors at once.

– written by Claude on Ben's behalf

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.97-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] [NO QA] Re-add allPolicies binding in SearchFiltersParticipantsSelector #92445

If no regressions arise, payment will be issued on 2026-06-10. 🎊

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.98-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] [NO QA] Re-add allPolicies binding in SearchFiltersParticipantsSelector #92445

If no regressions arise, payment will be issued on 2026-06-11. 🎊