audit fix #663
Triggered via pull request
September 17, 2026 06:35
na-trium-144
Status
Success
Total duration
1m 24s
Artifacts
–
node.js.yml
on: pull_request
Matrix: check-docs
Matrix: format
Matrix: lint
Matrix: test
Matrix: types
Annotations
15 warnings
|
test (22.x)
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
format (22.x)
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
check-docs (22.x)
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
types (22.x)
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint (22.x)
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint (22.x):
packages/runtime/tests/fileExecution.ts#L339
Expected an assignment or function call and instead saw an expression
|
|
lint (22.x):
packages/runtime/tests/fileExecution.ts#L289
Expected an assignment or function call and instead saw an expression
|
|
lint (22.x):
packages/runtime/tests/fileExecution.ts#L287
Expected an assignment or function call and instead saw an expression
|
|
lint (22.x):
packages/runtime/tests/fileExecution.ts#L221
Expected an assignment or function call and instead saw an expression
|
|
lint (22.x):
packages/runtime/tests/fileExecution.ts#L219
Expected an assignment or function call and instead saw an expression
|
|
lint (22.x):
packages/runtime/src/worker/runtime.tsx#L153
The ref value 'pendingPromises.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'pendingPromises.current' to a variable inside the effect, and use that variable in the cleanup function
|
|
lint (22.x):
app/sidebar.tsx#L118
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint (22.x):
app/navbar.tsx#L66
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint (22.x):
app/footer.tsx#L8
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
lint (22.x):
app/accountMenu.tsx#L80
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|