Follow-up from #1026.
That PR added a pyyaml regression guard measuring the templated Run step in .github/workflows/aeon.yml against the 21000-char GitHub expression limit. But the ci-tests trigger on.pull_request.paths / on.push.paths only list the root aeon.yml (the config file), not .github/workflows/aeon.yml.
Result: a workflow-only edit to the Run block (the exact regression this guards against) will not fire the guard unless the PR also touches scripts/** / bin/** / adapters.
Fix: add .github/workflows/aeon.yml to both path lists in ci-tests.yml.
Follow-up from #1026.
That PR added a pyyaml regression guard measuring the templated
Runstep in.github/workflows/aeon.ymlagainst the 21000-char GitHub expression limit. But theci-teststriggeron.pull_request.paths/on.push.pathsonly list the rootaeon.yml(the config file), not.github/workflows/aeon.yml.Result: a workflow-only edit to the Run block (the exact regression this guards against) will not fire the guard unless the PR also touches
scripts/**/bin/**/ adapters.Fix: add
.github/workflows/aeon.ymlto both path lists inci-tests.yml.