Repository navigation
Merge development → main (v1.3.3) - #43
Conversation
reqwest 0.13's rustls feature pulls in aws-lc-sys, whose C code fails on arm64_32 because it assumes 64-bit limbs on aarch64. ring fails there too, on its pointer-size asserts. On watchOS, ed-acp and ed-onde-account now use reqwest's native-tls (Security.framework) and ed-mcp uses rmcp's reqwest-native-tls, so no rustls crypto provider is built. Other platforms keep rustls with aws-lc. The workspace reqwest dependency no longer picks a TLS backend; each crate chooses one per target. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Use native-tls for reqwest on watchOS so arm64_32 builds
Co-Authored-By: siGit Code v1.6.6-acp <noreply@sigit.si> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Release 1.3.3
![sigit-code-review[bot]](https://avatars.githubusercontent.com/in/3492899?s=60&v=4){kind=small}
There was a problem hiding this comment.
This change promotes development to main at v1.3.3, bringing in a watchOS fix and a version bump. The main technical change is switching reqwest's TLS backend from rustls (aws-lc) to native-tls for watchOS targets, due to build failures and pointer size assertions in aws-lc/ring on arm64_32. This is implemented by conditionalizing reqwest and rmcp dependencies in ed-acp, ed-mcp, and ed-onde-account Cargo.toml files. The workspace version and all internal crate versions are bumped to 1.3.3. The reqwest dependency in the workspace root drops the rustls feature, leaving only json and stream, as TLS is now specified per-target. No code changes outside of Cargo.toml files are shown here.
Automated review by siGit Code Review · commit 8092ffb · see the review dashboard
Promotes development to main at v1.3.3.
Since main's last promotion this brings in the watchOS fix that switches reqwest to native-tls so arm64_32 builds (#41) and the 1.3.3 version bump (#42).