Fix Frontend Build Action

[JackHaeg]

Overview

The frontend build action is failing. This issue aims to identify and resolve the root cause to ensure successful builds.

Action Items

• Investigate the failure logs to determine the specific cause of the build issues.
  • Recent Failed frontend build on May 7, 2025
  • Log (See Resources / Instructions)
• Verify and update dependencies in the backend build configuration.
• Check GitHub Actions workflow files for misconfigurations and update them if necessary.
• Document any necessary changes for future reference.

Resources/Instructions

• GitHub Actions Documentation
• Review the latest CI logs in GitHub Actions under the repository’s Actions tab.
• Check the package.json (if applicable) or relevant dependency files for required updates.
• Refer to internal documentation for build and deployment processes.
• Error logs:

Error: Cache service responded with 422
    at Object.<anonymous> (/home/runner/work/_actions/jpribyl/action-docker-layer-caching/v0.1.0/dist/ttsc-dist/main.js/index.js:260:19)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/jpribyl/action-docker-layer-caching/v0.1.0/dist/ttsc-dist/main.js/index.js:184:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Error: Error: Cache service responded with 422```  

[JackHaeg]

@trillium continuing to look into this issue this week.

[lcchrty]

@trillium @JackHaeg quick update:

I was able to get it a NEW error.
I resolved the previous error by updating the following code:

    - name: Init Docker Cache
      uses: jpribyl/action-docker-layer-caching@v0.1.1

We were previously using v0.1.0.

It looks like I was able to build and push new images to ECR, but I have not deployed anything to dev.

The new error has to do with the version of the AWS SDK for JavaScript that we're using. It looks like it was deprecated in 2023. I'll look into it this week: