Its publish failed:
https://github.com/Traverse-Research/saxaboom/actions/runs/9953908044
We shouldn't use the link feature in the first place because saxaboom-runtime doesn't rely on any static functions, that's being solved in #21 and gfx-rs/metal-rs#330. We could also set the publish step to run on Mac or disable verification in the future.
For now I've published the crate with --no-verify (instead of logging in to crates.io on a Mac system):
cargo publish -p saxaboom-runtime --no-verify
(Note that this issue is mostly a note-to-self/reminder in case we do the next release before the corresponding PRs have been merged and released)
Its publish failed:
https://github.com/Traverse-Research/saxaboom/actions/runs/9953908044
We shouldn't use the
linkfeature in the first place becausesaxaboom-runtimedoesn't rely on any static functions, that's being solved in #21 and gfx-rs/metal-rs#330. We could also set the publish step to run on Mac or disable verification in the future.For now I've published the crate with
--no-verify(instead of logging in to crates.io on a Mac system):(Note that this issue is mostly a note-to-self/reminder in case we do the next release before the corresponding PRs have been merged and released)