This CI workflow was generated by running maturin generate-ci github (how handy!). But did require a bit of finagling to satisfy the dependency on OpenSSL (boo!). Specifically, I ran into https://github.com/sfackler/rust-openssl/issues/2036#issuecomment-1724324145. I also found that I needed to set the vendored feature flag on the openssl dependency in order to get building on Linux working.
To authorise to PyPI, we ended up using PyPI's Trusted Publishers feature, which the maturin publish command supports out of the box. This involved configuring this repo and workflow name in PyPI, and then removing the env: MATURIN_PYPI_TOKEN line from the generated CI config (solution referenced here).
I haven't tested this, but given that the config came from the maturin command directly, I have fairly high confidence. After this merges, I'll run the workflow manually on the v0.1.4 tag.
This CI workflow was generated by running
maturin generate-ci github(how handy!). But did require a bit of finagling to satisfy the dependency on OpenSSL (boo!). Specifically, I ran into https://github.com/sfackler/rust-openssl/issues/2036#issuecomment-1724324145. I also found that I needed to set thevendoredfeature flag on theopenssldependency in order to get building on Linux working.To authorise to PyPI, we ended up using PyPI's Trusted Publishers feature, which the
maturin publishcommand supports out of the box. This involved configuring this repo and workflow name in PyPI, and then removing theenv: MATURIN_PYPI_TOKENline from the generated CI config (solution referenced here).I haven't tested this, but given that the config came from the
maturincommand directly, I have fairly high confidence. After this merges, I'll run the workflow manually on thev0.1.4tag.