Release v0.6.0-rc.6
Pre-release
Pre-release
git-conventional changelog
Bug Fixes
- Proteus error system not working (at all)
- Force cargo to use git cli to avoid intermittent CI failures
Miscellaneous Tasks
- Updated rstest_reuse to 0.5
- Updated spinoff to 0.7
- Added codecov settings
- Update node to LTS 18 & enable JS e2e testing
- Make npm build run wasm-opt in Os
- Update JVM publish workflow to build on native platforms (#229)
IMPORTANT: The previous release (0.6.0-rc.5) is non-functional in general. The proteus error reporting does NOT work
There's a post mortem available here: #230 (comment)
- Fixed support for Proteus error codes
- WASM:
- all errors are now instances of
CoreCryptoError
which extends the standard JavaScriptError
but with additional properties:rustStackTrace
contains the original Rust error string.proteusErrorCode
contains the error code for Proteus calls. If it's 0, no error, otherwise it contains the code
- WASM/TS now has access to the
CoreCrypto.proteusLastErrorCode()
method which allows to retrieve the last-occured proteus error and thus brings it to parity with other FFIs
- all errors are now instances of
- On other platforms, the API is unchanged, but now works.
- WASM: