kingchenc
e595ea8bfe
Packaging fix for the `0.9.3` data layer. `0.9.3` published to crates.io, Maven Central, NuGet, npm, and the Go mirror, but the **Linux Python wheels failed to build**, so `Publish to PyPI` was skipped and no GitHub Release was attached. Root cause: the `live-binance` data layer links `native-tls` -> `openssl-sys`, and the `manylinux` / `musllinux` wheel-build containers do not ship the system OpenSSL headers. The native macOS and Windows wheels were unaffected (system TLS), which is why CI — running Python natively on the runners, where OpenSSL is present — stayed green. ### Changes - **`ci`**: install the OpenSSL headers inside the wheel container via maturin-action's `before-script-linux` (`openssl-devel` on `manylinux`, `openssl-dev` on `musllinux`) before maturin compiles. No library code changed. - **`release: bump 0.9.3 -> 0.9.4`**: version-string bump across the manual touchpoints + `CHANGELOG` `[0.9.4]`. `0.9.4` is functionally identical to `0.9.3`; it exists only because the already- published registries cannot re-release `0.9.3`. PyPI publishes for the first time starting at `0.9.4` (it skips `0.9.3`).
28 lines
606 B
JSON
28 lines
606 B
JSON
{
|
|
"name": "wickra-linux-arm64-gnu",
|
|
"version": "0.9.4",
|
|
"description": "Native binding for wickra (linux arm64 GNU). Installed automatically as an optional dependency of wickra on matching platforms.",
|
|
"main": "wickra.linux-arm64-gnu.node",
|
|
"files": [
|
|
"wickra.linux-arm64-gnu.node"
|
|
],
|
|
"license": "MIT OR Apache-2.0",
|
|
"engines": {
|
|
"node": ">= 18"
|
|
},
|
|
"os": [
|
|
"linux"
|
|
],
|
|
"cpu": [
|
|
"arm64"
|
|
],
|
|
"libc": [
|
|
"glibc"
|
|
],
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/wickra-lib/wickra"
|
|
},
|
|
"homepage": "https://github.com/wickra-lib/wickra"
|
|
}
|