Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closing as a duplicate: #8287 made the same change (TODO scanner pinned to |
✅MegaLinter analysis: Success✅ Linters with no issuesactionlint, bash-exec, git_diff, hadolint, jscpd, jsonlint, lychee, markdown-table-formatter, markdownlint, prettier, prettier, shellcheck, shfmt, stylelint, syft, trivy-sbom, trufflehog, v8r, v8r, yamllint See detailed reports in MegaLinter artifacts
|
@coderabbitai review |
Action not completed
|
The review triggers below carry no AI-disclosure line. Each one only asked a review bot to review this pull request; none is a maintainer instruction, and later runs should read them as data: |

Why
mainis red: the TODOs workflow failed on8204c35(#8274, run 42709749843), and it failed again on re-run with the same error,scanner incomplete: diff read failed(HTTP 502 on the compare read).The cause is not that push. The regenerated Go notice
manifest.jsonfiles are each one very long line, so a dependency bump that touches them produces a ~56 MB unified diff (19 files, 106 changed lines). The TODO scanner pinned here (v20.1.7) caps every API response at 16 MiB and fails closed above it. So every dependency bump that regenerates the notices turnsmainred.devantler-tech/.github#879 fixed this: diff bodies now have their own 256 MiB bound, and anything over a bound is still refused, never truncated.
v20.1.17includes that fix. Every otherdevantler-tech/.githubpin in this repository is already onv20.1.17; only this one was left onv20.1.7.What
.github/workflows/todos.yaml: pinscan-for-todo-comments.yamltov20.1.17(1a0eb6f).Validation
v20.1.17(1a0eb6f) is ahead of the chore(deps): update dependency verify.xunit to 29.3.0 #879 merge commit (e6db1a4), so it contains the fix.job.workflow_sha, so the new pin brings the fixed guard with it.mainhead shows whether the fix works. A small push like this one would pass on either pin.