fix(landing): restore EXPLORE auth flow on Fundamental Blocks logo #395
imjustinliaodeploy-frontend-aws.yml
on: push
Lint & Code Quality
49s
Security Audit
34s
Secret Scan (Gitleaks)
46s
Build Verification
51s
Deploy to AWS
1m 34s
Annotations
16 warnings
|
Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Secret Scan (Gitleaks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint & Code Quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint & Code Quality
Found console.log statements - consider removing for production
|
|
Lint & Code Quality:
frontend/src/components/app/RouteLoadingSkeleton.tsx#L43
'_text' is defined but never used
|
|
Lint & Code Quality:
frontend/src/components/app/OnboardingModal.tsx#L387
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 & Code Quality:
frontend/src/components/app/MessageList.tsx#L84
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 & Code Quality:
frontend/src/components/app/ChatInput.tsx#L534
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 & Code Quality:
frontend/src/components/app/ChatInput.tsx#L198
React Hook useCallback has a missing dependency: 'hasContentTypes'. Either include it or remove the dependency array
|
|
Lint & Code Quality:
frontend/src/components/app/ChatInput.tsx#L86
'isPreparing' is assigned a value but never used
|
|
Lint & Code Quality:
frontend/src/components/app/AppContentRouter.tsx#L128
React Hook useEffect has missing dependencies: 'conversation' and 'upsertConversation'. Either include them or remove the dependency array
|
|
Lint & Code Quality:
frontend/src/app/demo/page.tsx#L376
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 & Code Quality:
frontend/src/app/demo/page.tsx#L305
Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
Lint & Code Quality:
frontend/src/app/demo/page.tsx#L4
'Play' is defined but never used
|
|
Build Verification
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Deploy to AWS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
frontend-audit-report
Expired
|
321 Bytes |
sha256:c25609a5f20c61055761c4127071cfcf1680df87226fd2efcb0318096c5e7139
|
|
|
frontend-build
Expired
|
56.3 MB |
sha256:059b055062f2a172f29a1a8616d139f05b03757e62b499d7b7b1c579227d5d66
|
|
|
frontend-gitleaks-report
Expired
|
6.53 KB |
sha256:cadfa73805727eae96a2bd6b776b8c31c649a9ff89b95aab646b75b2b4ec71e3
|
|