Skip to content

Release v0.5.0: API Adjustments

Compare
Choose a tag to compare
@OtaK OtaK released this 14 Sep 13:00
eb4e6c1

[0.5.0] - 2022-14-09

git-conventional changelog

Bug Fixes

  • Rollback openmls & chrono in order to release 0.5.0
  • Pin openmls without vulnerable chrono
  • Wee_alloc memory leak + NPM publish issue
  • Unreachable pub struct breaks docgen
  • Fixed iOS SQLCipher salt handling within keychain
  • [breaking] Changed misleading callback API and docs
  • [breaking] Added missing TS API to set CoreCrypto callbacks
  • Force software implementation for sha2 on target architectures not supporting hardware implementation (i686 & armv7 in our case)

Documentation

  • Add forgotten 0.4.0 changelog

Features

  • [breaking] 'commit_pending_proposals' now returns an optional CommitBundle when there is no pending proposals to commit

Miscellaneous Tasks

  • Release v0.5.0 Redux
  • Update UniFFI to 0.20
  • Release v0.5.0
  • Update node version from 12 to 16 LTS
  • Update dependencies
  • Remove es2020-specific operators and target es2020 only
  • Updated changelog
  • [BREAKING]: commit_pending_proposals now returns an optional CommitBundle
    • This was made to handle the case where there are no queued proposals to commit and this method would be called, causing the operation to fail.
  • [BREAKING]: Changed the API for callbacks for clarity
    • This also contains documentation changes that make the use and intent of callbacks easier to understand.
  • Fixed the iOS-specific database salt handling to allow using several databases on the same device.
  • TypeScript bindings:
    • Removed the use of ES2020-specific operators (?? Null-coalescing operator) to allow downstream to compile without transpiling.
    • Added callbacks API
    • Removed the usage of wee_alloc allocator as it leaks memory: rustwasm/wee_alloc#106
  • Kotlin & Swift bindings:
    • Upgraded UniFFI to 0.20 which now generates a correct callback interface in camelCase instead of erroneous snake_case.
      • Note that you will have to adapt to the aforementioned breaking changes to the callback API anyway so this just makes it a bit nicer