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
I just came across this warning in my CI workflow's summary (originating from job that builds x86_64 target on macos-12):
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see actions/runner-images#10721
So, I was wondering if it is ok to migrate to macos-14 instead? I don't own a Mac to test/build locally.
Your maturin version (maturin --version)
v1.7.4
Your Python version (python -V)
3.12.6
Your pip version (pip -V)
whatever is setup in runner's tool cache (using python-version: 3.x)
What bindings you're using
pyo3
Does cargo build work?
Yes, it works
If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash /)?
Yes
Steps to Reproduce
Run maturin generate-ci on existing project or maturin new <pkg-name>
Push generated workflow to GitHub remote
Review workflow run's summary. Notice the "Annotations" section below the workflow's diagram.
The text was updated successfully, but these errors were encountered:
Oh I didn't see that PR. For the record, I did do a 'macos' search on open/closed issues/discussions. I didn't think to check PRs though. Glad to see you folks are already tracking it. I guess I'll leave this open since it will auto-close when #2246 is merged.
Bug Description
I just came across this warning in my CI workflow's summary (originating from job that builds x86_64 target on macos-12):
So, I was wondering if it is ok to migrate to macos-14 instead? I don't own a Mac to test/build locally.
Your maturin version (
maturin --version
)v1.7.4
Your Python version (
python -V
)3.12.6
Your pip version (
pip -V
)whatever is setup in runner's tool cache (using
python-version: 3.x
)What bindings you're using
pyo3
Does
cargo build
work?If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash
/
)?Steps to Reproduce
maturin generate-ci
on existing project ormaturin new <pkg-name>
The text was updated successfully, but these errors were encountered: