chore: release v0.19.1#417
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 884359f. Configure here.
| actual, expected, | ||
| "listener should be notified {expected} times" | ||
| ); | ||
| } |
There was a problem hiding this comment.
Timeout uses stale listener count
Medium Severity
In wait_for_listener_count, the timeout branch compares expected to actual from the start of the loop iteration, not a fresh load. If the background notify thread increments the counter after that load but before the deadline check, the assertion can fail even though the listener already reached the expected count, causing intermittent test failures.
Reviewed by Cursor Bugbot for commit 884359f. Configure here.
884359f to
6ef5b25
Compare


🤖 New release
walletkit-db: 0.19.0 -> 0.19.1walletkit-core: 0.19.0 -> 0.19.1 (✓ API compatible changes)walletkit: 0.19.0 -> 0.19.1 (✓ API compatible changes)Changelog
walletkitThis PR was generated with release-plz.
Note
Low Risk
Patch release with version and changelog updates plus test-only synchronization changes; no production logic changes in this diff.
Overview
Release v0.19.1 bumps workspace and crate versions from
0.19.0to0.19.1(Cargo.toml,Cargo.lock) and documents 0.19.1 inwalletkit/CHANGELOG.md, citing support for World ID walletkit user agents (#416).Separately, vault-changed listener tests in
credential_storage.rsreplace fixedthread::sleepdelays with await_for_listener_counthelper that polls the notification counter (up to 1s) so assertions wait for the background notify thread instead of racing it.Reviewed by Cursor Bugbot for commit 884359f. Bugbot is set up for automated code reviews on this repo. Configure here.