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
Once mosdef-hub/mbuild#1180 passes I think we should do the same here; adding python 3.12 to the CI workflow, updating the .yml files to include python 3.12 and make sure the feedstock for the next release includes 3.12 as well.
Also in the PR linked, I mention how macOS-latest is now an ARM based image of Mac, so if we want to test both ARM and intel we'll have to add macOS-13 to the os-matrix, we should probably do that here as well.
The text was updated successfully, but these errors were encountered:
Before we can do this, we might have to make a new release of mBuild. If we try to install mbuild from anaconda with python pinned at 3.12 we'll get mbuild 0.16.4 which won't work with python 3.12.
Another thing to remember for this is the changes to the MacOS images used in the CI workflow. If we want to test MacOS x86 we need to add macos-13 to the os-matrix.
Once mosdef-hub/mbuild#1180 passes I think we should do the same here; adding python 3.12 to the CI workflow, updating the
.yml
files to include python 3.12 and make sure the feedstock for the next release includes 3.12 as well.Also in the PR linked, I mention how
macOS-latest
is now an ARM based image of Mac, so if we want to test both ARM and intel we'll have to addmacOS-13
to the os-matrix, we should probably do that here as well.The text was updated successfully, but these errors were encountered: