@Elliott @Kavita Nambissan @Ayush fixes were pushed in 2.7.13 for build dependencies, and the the new release is pushed and tagged. can you please let us know if 2.7.13 helps your own build issues?

Thanks @Colin - Krumware! Will try the updated version in a bit and post back with success status

Fine for me up to 2.7.14 🙏🏽

@Colin - Krumware - Apologies for the late reply, was not able to get to this earlier 🙏. I tried building this, but now everything is failing. The Vercel build for Calcom is failing with

≫   UNKNOWN_ERROR: Error: Command failed: npx turbo run build --filter=@calcom/web...[57d4481e50744edf7d80251f4f94428ae2ca0491] --dry=json
ERROR  run failed: failed to resolve packages to run: git error: object not found - no match for id (6e5c3a88eea8114d2184d513d8dc34ea9fa2982d); class=Odb (9)
....
➤ YN0000: ┌ Post-resolution validation
➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
➤ YN0000: └ Completed in 0s 297ms
➤ YN0000: Failed with errors in 1s 309ms
Error: Command "yarn install" exited with 1
Deployment completed
BUILD_UTILS_SPAWN_1: Command "yarn install" exited with 1

The docker build in the EC2 now fails at

yarn install

step in the docker, and locally it continues to fail at

Collecting page data...

EC2 error

#0 95.46 ➤ YN0013: │ object.fromentries@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
#0 95.46 ➤ YN0013: │ object.assign@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry
#0 95.46 ➤ YN0013: │ object.entries@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
#0 95.46 ➤ YN0013: │ object.entries@npm:1.1.6 can't be found in the cache and will be fetched from the remote registry
#0 95.46 ➤ YN00
#0 95.46 [output clipped, log limit 1MiB reached]
------
failed to solve: executor failed running [/bin/sh -c yarn install]: exit code: 1

Local

#0 104.3 @calcom/web:build: prisma:query SELECT "public"."App"."slug" FROM "public"."App" WHERE 1=1 OFFSET $1
#0 104.4 @calcom/web:build: prisma:query COMMIT
#0 109.7 @calcom/web:build: ERROR: command finished with error: command (/calcom/apps/web) yarn run build exited (129)
#0 109.7 command (/calcom/apps/web) yarn run build exited (129)
#0 109.7
#0 109.7  Tasks:    5 successful, 6 total
#0 109.7 Cached:    0 cached, 6 total
#0 109.7   Time:    1m48.788s
#0 109.7
#0 109.7  ERROR  run failed: command  exited (129)

I'll check to see if reverting back to the previous version at least gets the EC2 build to get to the Collecting pages error which is the

turbo run build

step..

@Kavita Nambissan what are the specs of the machine that is running the build, could it be running out of memory?