Skip to content

Remove print statement for response logging #4

Remove print statement for response logging

Remove print statement for response logging #4

Triggered via push June 4, 2026 19:06
Status Success
Total duration 5m 26s
Artifacts 2
Matrix: Test
Deploy to Lambda Feedback  /  Setup
8s
Deploy to Lambda Feedback / Setup
Deploy to Lambda Feedback  /  ...  /  build
Deploy to Lambda Feedback / deploy-staging / build-aws / build
Deploy to Lambda Feedback  /  ...  /  Deploy (staging)
9s
Deploy to Lambda Feedback / deploy-staging / deploy-staging-aws / Deploy (staging)
Deploy to Lambda Feedback  /  Await Manual Approval (Production)
Deploy to Lambda Feedback / Await Manual Approval (Production)
Deploy to Lambda Feedback  /  ...  /  Checkout Code
Deploy to Lambda Feedback / deploy-production / Checkout Code
Deploy to Lambda Feedback  /  ...  /  Determine Version
Deploy to Lambda Feedback / deploy-production / Determine Version
Deploy to Lambda Feedback  /  ...  /  Create Git Tag
Deploy to Lambda Feedback / deploy-production / Create Git Tag
Deploy to Lambda Feedback  /  ...  /  build
Deploy to Lambda Feedback / deploy-production / build-aws / build
Deploy to Lambda Feedback  /  ...  /  Create GitHub Release
Deploy to Lambda Feedback / deploy-production / Create GitHub Release
Deploy to Lambda Feedback  /  ...  /  deploy
Deploy to Lambda Feedback / deploy-production / deploy-production-aws / deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test (3.13)
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-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Lambda Feedback / Setup
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 will be forced to run with Node.js 24 by default starting June 16th, 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 Lambda Feedback / deploy-staging / build-aws / Build (staging) & Push on AWS ECR
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Lambda Feedback / deploy-staging / deploy-staging-aws / Deploy (staging)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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
lambda-feedback~chat-function-boilerplate~TN1IFO.dockerbuild
93.5 KB
sha256:e67892ed6105e723a311edebc5df70dd0d448da4aac4ae61e48398dd6f36b371
test-results
495 Bytes
sha256:1ab7c9677277b542f59da889e5257f22527a90127828177af13d89cbec5b267f