Skip to content

fix: eliminate dead-code false positives from optimistic effect classification #496

fix: eliminate dead-code false positives from optimistic effect classification

fix: eliminate dead-code false positives from optimistic effect classification #496

Triggered via pull request August 2, 2026 05:31
Status Failure
Total duration 1m 3s
Artifacts

ci.yml

on: pull_request
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
ci (1.20, 29)
Process completed with exit code 10.
ci (1.19, 27)
The strategy configuration was canceled because "ci._1_20_29" failed
ci (1.19, 27)
The operation was canceled.
ci (1.20, 29)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (1.20, 29): lib/reach/check/dead_code.ex#L61
Function body is nested too deep (max depth is 2, was 3).
ci (1.20, 29): test/reach/reach_test.exs#L567
Nested modules could be aliased at the top of the invoking module.
ci (1.20, 29): test/reach/reach_test.exs#L615
Nested modules could be aliased at the top of the invoking module.
ci (1.20, 29): lib/reach/check/dead_code.ex#L61
Nested modules could be aliased at the top of the invoking module.
ci (1.19, 27)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/