Skip to content

v0.22.7 — Log ZApi/ZApiLite unsubscribe calls in parity with logout (PR #78)

Choose a tag to compare

@dmorinigoFunnelchat dmorinigoFunnelchat released this 07 Oct 19:42
· 46 commits to production since this release
Immutable release. Only release title and notes can be modified.
8f8fe6f

ZApiClient::unsubscribe() was the only client method making its HTTP calls (disconnect + integrator cancel) without logRequest(), so a failed unsubscribe left no device_logs trace — the record needed to detect a paid instance billed but never cancelled. Both calls now log in parity with logout(); both URLs carry /token/<token>/ which sanitizeUrl() masks, so no credential is persisted. step (disconnect|cancel) distinguishes the two within method=unsubscribe. Inherited by ZApiLite. Additive, backward-compatible.

Consumers on ^0.22.4 (e.g. accounts) can bump to pick up the root-cause logging.