Thanks for the PR,@dbarabashh!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	ed93f1c
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/69245dcc3bcf750008b9b03c
😎 Deploy Preview	https://deploy-preview-11760--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 96 (🔴 down 1 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify project configuration.

View yourCI Pipeline Execution ↗ for commited93f1c

☁️Nx Cloud last updated this comment at2025-11-24 13:50:21 UTC

Codecov Report

❌ Patch coverage is28.57143% with20 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.50%. Comparing base (78858ee) to head (ed93f1c).
⚠️ Report is 3 commits behind head on main.

❌ Your patch status has failed because the patch coverage (28.57%) is below the target coverage (90.00%). You can increase the patch coverage or adjust thetarget coverage.

@@            Coverage Diff             @@##             main   #11760      +/-   ##==========================================- Coverage   90.52%   90.50%   -0.02%==========================================  Files         522      522                Lines       53353    53344       -9       Branches     8921     8910      -11     ==========================================- Hits        48296    48280      -16- Misses       5040     5047       +7  Partials       17       17

🤔 I don't get these failures locally. Re-running...

@JoshuaKGoldberg can you help with github actions? I can't reproduce this locally. Locally everything passes and everything is ok

Blurgh, yes, I also don't reproduce them locally. We can ignore them in this PR for now - let's just pretend the build is passing. In parallel I'll try to clear the Nx cache and work with@JamesHenry on#11593.

I did two items of repo housekeeping to resolve the CI build issue:

• Removed the oldSKIP_AST_SPEC_REBUILD env var:c2ee584
  • Based on how it was being checked it was doing the opposite of what the name implied, and it was also imperatively triggering tasks nested inside the task graph which is always going to be a recipe for subtle issues
• Fixed the project graph to accurately reflect the fact that the ast-spec is implicitly depended upon by essentially everything else:348e7d7

Before

ast-spec was orphaned without any traced relationships, which clearly is not correct

After

ast-spec is appropriately one of the core nodes at the base of the graph

@JoshuaKGoldberg youleft a comment here and I removed those tests but now there’s a problem with the coverage rate