Hi @hrishikesh thanks for your response. That provided the missing piece I was having trouble confirming. I did try some build optimization but was still running into issues.
After some digging I believe my issues is possibly related to PQR (Parallel Query Running) as you suggested in this thread: Gatsby v4 Builds suddenly killed, exit code 137 - #6 by hrishikesh as I also updated to Gatsby 4 recently.
Trying the flag GATSBY_CPU_COUNT as was suggested in this: Gatsby v4 memory usage during Parallel Query Running · Discussion #34215 · gatsbyjs/gatsby · GitHub looks like it resulted in a successful build so I think at this point any additional troubleshooting I do is going to be PQR related. Thanks for your help again!