You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ffi layer and possibly the main payjoin crate with #888
Question
With the introduction of macos-15 runners as the latest github is planning on sunsetting macos-13 runners which means we won't have a reliable way of build x86_64 based mac architecture.
Nice find! IIRC the only thing preventing us from using later macos images was that the Docker action didn't support it. Since we plan on dropping the Docker dependency, and already disabled the integration test from macOS jobs, we should be able to upgrade immediately to macos-latest.
We should probably keep building cross-compat targets to support devs who are still on x86 for the foreseeable future. I think we could run both cargo build commands in parallel with something like:
Activity
spacebear21 commentedon Aug 21, 2025
Nice find! IIRC the only thing preventing us from using later macos images was that the Docker action didn't support it. Since we plan on dropping the Docker dependency, and already disabled the integration test from macOS jobs, we should be able to upgrade immediately to macos-latest.
benalleng commentedon Aug 21, 2025
How do we want to deal with the lipo create building the cross-compatible targets?
spacebear21 commentedon Aug 21, 2025
We should probably keep building cross-compat targets to support devs who are still on x86 for the foreseeable future. I think we could run both
cargo buildcommands in parallel with something like:This works locally, I'm just not sure whether it will cause problems with the low-spec gh runner
benalleng commentedon Aug 21, 2025
Ok, just wanted to make sure that we can still build a x86_target even without access to a x86 mac
spacebear21 commentedon Aug 25, 2025
Closed by #988 and #989 , we're now using macos-latest.