fix: stabilize subagent settings and goal compaction (#192) #792
elkaixci.yml
on: push
Matrix: test
build
3m 31s
test-pi-tui
1m 1s
test-windows
lint
59s
typecheck
2m 29s
test
3s
Annotations
19 warnings
|
lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
eslint(no-console):
packages/agent-core-v2/src/_base/di/lifecycle.ts#L640
Unexpected console statement.
|
|
eslint(no-console):
packages/agent-core-v2/src/_base/di/lifecycle.ts#L558
Unexpected console statement.
|
|
eslint-plugin-unicorn(prefer-string-replace-all):
packages/protocol/src/asyncapi.ts#L135
Prefer `String#replaceAll()` over `String#replace()` when using a regex with the global flag.
|
|
eslint-plugin-unicorn(prefer-string-replace-all):
packages/protocol/src/asyncapi.ts#L135
Prefer `String#replaceAll()` over `String#replace()` when using a regex with the global flag.
|
|
eslint-plugin-unicorn(catch-error-name):
packages/agent-core-v2/src/_base/errors/unexpectedError.ts#L28
The catch parameter "err" should be named "error"
|
|
eslint-plugin-unicorn(catch-error-name):
packages/agent-core-v2/src/_base/errors/unexpectedError.ts#L20
The catch parameter "handlerErr" should be named "error"
|
|
eslint(no-console):
packages/agent-core-v2/src/_base/errors/unexpectedError.ts#L21
Unexpected console statement.
|
|
eslint(no-console):
packages/agent-core-v2/src/_base/errors/unexpectedError.ts#L4
Unexpected console statement.
|
|
eslint(no-loop-func):
packages/agent-core-v2/src/_base/event.ts#L211
Function declared in a loop contains unsafe references to variable(s)
|
|
eslint(no-loop-func):
packages/agent-core-v2/src/_base/event.ts#L206
Function declared in a loop contains unsafe references to variable(s)
|
|
test-pi-tui
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
typecheck
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|