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
{{ message }}
Repository navigation
CI moved from macos-14 to macos-15; next release will ship macos-15-built macOS MATLAB binaries #31
GitHub retires the macos-14 runner image on November 2, 2026. #30 (merged) moved the macOS MATLAB MEX jobs in test.yml and release.yml to macos-15.
We are deliberately not minting a new version yet. The current release, v0.4.1, ships macOS MATLAB binaries that were built on macos-14 with MATLAB R2024b. We want to keep those available, unchanged, as long as possible.
What changed in CI
The macOS MATLAB build now runs on macos-15 with MATLAB R2025a and an Xcode 16.x toolchain. macos-15 images only ship Xcode 16 and newer, and R2024b's mex needs Xcode 15.
Linux and Windows MATLAB builds, toolbox packaging, and the Python wheel jobs are unchanged. The macOS Python wheels were already built on macos-latest.
What this means for the next release
macos-14 runners will be gone by the next version increment, so that release will have to use the macos-15 / R2025a-built macOS MATLAB binaries. Affected assets:
pyraview.mexmaca64
pyraview-macOS-ARM64.zip
the macOS MEX inside Pyraview.mltbx
A MEX built with R2025a may not load in older MATLAB releases on Apple Silicon Macs. Mac users still on R2024b may need to stay on v0.4.1 or upgrade MATLAB.
Caution: don't rebuild v0.4.1
Don't run the release.yml manual "Tag to release" dispatch for v0.4.1 or any other existing tag. A dispatch uses the current workflow on main. It would rebuild the macOS MEX with R2025a on macos-15 and likely overwrite the macos-14-built assets we want to keep.
Activity