2.0.0

What's Changed

• fix: speed up validation tests by @ganchoradkov in #1515
• chore: a comment to explain why await is ommited by @ganchoradkov in #1516
• chore: adds universal-provider to workspaces by @ganchoradkov in #1517
• fix(core): fixes missing isInitialized check on store.getAll by @bkrem in #1523
• fix: universal provider required test params by @ganchoradkov in #1524
• fix(deps): fixes stale keyvaluestorage storage due to types deps by @bkrem in #1535
• feat: Pairing API by @bkrem in #1536

Important changes when upgrading from 2.0.0-rc.x to 2.0.0 (stable)

• Pairings are now managed by the Pairing API (see docs)
• We recommend accessing all pairing-related values and methods via the SignClient.core.pairing interface going forward.
• BREAKING CHANGE: Pairing events (pairing_create, pairing_delete, pairing_expire) are now managed by the core/pairing EventEmitter:
  • Before: signClient.on(“pairing_delete”, …)
  • After: signClient.core.pairing.events.on(“pairing_delete”, …)
• Pairing methods are now managed by the core/pairing controller:
  • Before: signClient.pair(…)
  • After: signClient.core.pairing.pair(…)
  • Calling pairing-specific methods directly on signClient will continue to work, but is considered deprecated and will be removed in a future major version.
• Pairing values are now managed by the core/pairing controller and have a dedicated getter: signClient.core.pairing.getPairings()
  • Accessing stored pairings via SignClient.pairing will continue to work, but is considered deprecated and will be removed in a future major version.

Full Changelog: 2.0.0-rc.4...2.0.0