Build with macos-13: https://github.com/yao-pkg/pkg-fetch/actions/runs/10612829797

Build with macos-14 for arm: https://github.com/yao-pkg/pkg-fetch/actions/runs/10615039683

I am not sure but according to this https://github.com/actions/runner-images?tab=readme-ov-file#available-images
macos-13 should be intel?
and
macos-14 should be arm?

@axi92 Should be yeah but seems that macos-arm build are failing when using macos-14

@faulpeltz this is another blocker, macos build fails: #40 (comment)

I have jsut triggered a new build let's see how that goes

New try:

https://github.com/yao-pkg/pkg-fetch/actions/runs/10702596743

https://github.com/yao-pkg/pkg-fetch/actions/runs/10703084714

Cool new issue: nodejs/node#52230

Seems runner run out of RAM, new try with a limit on jobs:

https://github.com/yao-pkg/pkg-fetch/actions/runs/10717836953

With the fix now the x64 seems working but the arm64 is still failing. Try to re-enable cross build with less jobs:

https://github.com/yao-pkg/pkg-fetch/actions/runs/10722148089

Try to use pip for nodejs 18 and brew on 20:

https://github.com/yao-pkg/pkg-fetch/actions/runs/10722955285

Everything is green 🎉 🎉 🎉 🎉