v0.21.1

0.21.1 (2026-11-04)

Bug Fixes

• 18.4: own the session and the secure-storage hold across a recreation (#605) (0b43043)
• deps: override tinypool and serialize-javascript in the docs site (#625) (9066fc6)

v0.21.0

0.21.0 (2026-10-31)

Features

• 18.2: charge queued work's faults to the dispatch that queued it (#596) (d246778), closes #500

Bug Fixes

• 18.3: queue same-key secure-storage requests behind a pending prompt (#599) (2eb3f22)

v0.20.3

0.20.3 (2026-10-28)

Bug Fixes

• 18.1: fix the CI flakes at their causes (#584) (5a7ab54)

v0.20.2

0.20.2 (2026-10-22)

Bug Fixes

• 17.7: a denied storage prompt completes on its executor, and every M17 pin has a recorded red (#545) (262177c)

v0.20.1

0.20.1 (2026-10-18)

Bug Fixes

• 17.4: android redacts app text in logcat, and the slow-handler warning names the app's handler (#523) (41af910)
• 17.5: no local test run hangs silently, tests a stale library, or fails bare (#528) (2f88924)

v0.20.0

0.20.0 (2026-10-15)

⚠ BREAKING CHANGES

• 17.1: in #464's scenario the window dispatch now returns its own rc, and the continuation's fault arrives as its own dispatch's FaultNotice under its own handler id. It used to return rc 0 with the continuation's fault reported under the window's id, and the window's own synchronous fault was lost.

Bug Fixes

• 17.1: a fault from an inline continuation is its own dispatch's (#503) (00976fd)
• 17.2: biometrics and secure storage leave hostCallBegin for their own executors on Android (#507) (31af87c)
• 17.3: a recreated activity never shows the old page's frame (#510) (6aa6809)

v0.19.0

0.19.0 (2026-10-03)

⚠ BREAKING CHANGES

• deps: apps built on BlazorNative now require iOS 15.0 or later. iOS 13 and iOS 14 devices are no longer supported.

Bug Fixes

• deps: update dependency kingfisher to v8.13.0 and raise the iOS floor to 15.0 (#376) (3308aed)

v0.18.0

0.18.0 (2026-10-03)

⚠ BREAKING CHANGES

• 16.7: blazornative_dispatch_event rc reports only the synchronous part of a handler. Since 0.17.0 rc 0 means the handler did not fault in its synchronous part, not that it finished. Since this release a fault after the handler began a host call or a fetch arrives as a FaultNotice host-call op with rc 0, where a call the shell answered inside begin used to give rc 2. Shells must route FaultNotice to their error handler, as both shipped shells do.

Bug Fixes

• 16.7: a fault after a handler began a shell call is a FaultNotice (#465) (dc5b737)

v0.17.2

0.17.2 (2026-10-02)

Bug Fixes

• deps: update dependency androidx.activity:activity to v1.13.0 (#433) (af8297b)
• deps: update dependency androidx.core:core to v1.19.1 (#353) (ff813f5)

v0.17.1

0.17.1 (2026-10-02)

Bug Fixes

• 16.4: the lost first tap, a harness race and a cold LAContext on the render thread (#449) (3f432a3)