ReenigneArcher

I don't know what changed, but this is working now.

I have re-run it in debug mode: https://github.com/ReenigneArcher/brew-error-reproduction/actions/runs/8870403949/job/24376380948 I have not tried refactoring the workflow yet, but I know that the brew install would at least succeed if it were...

Re-ordering the workflow won't be feasible due to it requiring the build to run after this action is initialized: https://github.com/orgs/community/discussions/68044#discussioncomment-7109477 Mostly this is due to me using a single code-ql...

Just checking in. This is still occurring: https://github.com/ReenigneArcher/brew-error-reproduction/actions/runs/9916092767/job/27397917114#step:3:66

@angelapwen Thank you for looking into this. I am pretty sure I tried the suggestion in the logs (`arch -arm64 brew install ...`) previously and it did not help... I...

Sorry for the delay... When using the suggestion from the logs (https://github.com/ReenigneArcher/brew-error-reproduction/pull/2), I get the following error: ``` arch: posix_spawnp: brew: Bad CPU type in executable ``` https://github.com/ReenigneArcher/brew-error-reproduction/actions/runs/11108869334/job/30862839806?pr=2#step:3:48 Interesting since...

Just following up to hopefully keep this on the radar. The macos-12 image is about to removed. macos-13 will likely be EOL in October 2025, so there's still a little...

This issue (https://github.com/msys2/MINGW-packages/issues/20407) affects Vite >= 5.x; but 4.x is working fine. Looking at the git blame of their `package.json` it appears after they bumped rollup from 4.2 to 4.13....

@dependabot rebase

@dependabot rebase