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-07-30] Investigate workflow job failing on main: lint / ESLint check #96753
🐛 Error Message:
warning: [git-mirror] Skipping cache commit: Found 2 failed/cancelled steps
warning: [git-mirror] - Step: unknown (failed)
failure: Process completed with exit code 1.
⚠️Action Required⚠️:
🛠️ A recent merge appears to have caused a failure in the job named lint / ESLint check.
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.
Investigated — the lint failure is a latent error surfaced by an ESLint cache bust, not a regression from the triggering PR.
Root cause chain:
eslint-config-expensify 4.0.7 added notation/annotation to the no-negated-variables exception list. buildDotNotationPath in scripts/utils/TSCompilerUtils.ts was previously a false positive ("Notation" contains "not") and carried an eslint-disable directive. With the rule fixed, that directive became unused, which ESLint reports as an error.
The config bump PR passed lint on main because the ESLint cache is keyed on config files and file contents, not plugin internals — the stale cached result for TSCompilerUtils.ts masked the new error.
The Node 26 upgrade PR changed package-lock.json/.nvmrc, which invalidated the cache. The post-merge run re-linted the file and surfaced the error. The workflow's cold-cache retry also failed, confirming it's a real lint error rather than a cache artifact — the Node 26 PR was just the unlucky trigger.
Fix:#96758 removes the now-unused directive (one-line change, verified locally that lint passes on the file).
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.43-1 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-07-30. 🎊
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
NicolasBonet commentedon Jul 22, 2026
Investigated — the lint failure is a latent error surfaced by an ESLint cache bust, not a regression from the triggering PR.
Root cause chain:
eslint-config-expensify4.0.7 addednotation/annotationto theno-negated-variablesexception list.buildDotNotationPathinscripts/utils/TSCompilerUtils.tswas previously a false positive ("Notation" contains "not") and carried aneslint-disabledirective. With the rule fixed, that directive became unused, which ESLint reports as an error.mainbecause the ESLint cache is keyed on config files and file contents, not plugin internals — the stale cached result forTSCompilerUtils.tsmasked the new error.package-lock.json/.nvmrc, which invalidated the cache. The post-merge run re-linted the file and surfaced the error. The workflow's cold-cache retry also failed, confirming it's a real lint error rather than a cache artifact — the Node 26 PR was just the unlucky trigger.Fix: #96758 removes the now-unused directive (one-line change, verified locally that lint passes on the file).
NicolasBonet commentedon Jul 22, 2026
Worflows resolved: https://github.com/Expensify/App/actions/runs/29933084884
melvin-bot commentedon Jul 23, 2026
@NicolasBonet
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.43-1 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-07-30. 🎊
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]
[-]Investigate workflow job failing on main: lint / ESLint check[/-][+][Due for payment 2026-07-30] Investigate workflow job failing on main: lint / ESLint check[/+]