@@ -6,6 +6,59 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66and this project adheres to
77[ Semantic Versioning] ( https://semver.org/spec/v2.0.0.html ) .
88
9+ ## [ 1.9.2] - 2024-05-29
10+
11+ ### :chart_with_upwards_trend : Improvements
12+
13+ - ESP-IDF:
14+
15+ - Fix CLI command, ` memfault_ota_check ` , to return 0 to the console component
16+ when an update is available.
17+
18+ - Add the temperature metric ` cpu_temp ` which is measured using an internal
19+ temperature sensor that many ESP32 boards have built-in. This metric is
20+ collected by default with the Kconfig ` CONFIG_MEMFAULT_METRICS_CPU_TEMP=y ` .
21+
22+ - Enable recording vprintf data into the Memfault log buffer through a vprintf
23+ hook. Users can call ` memfault_esp_port_vprintf_log_hook() ` from their
24+ vprintf handler so they can use both their vprintf handler and record logs
25+ into Memfault's log buffer. To use this feature, set
26+ ` CONFIG_MEMFAULT_LOG_USE_VPRINTF_HOOK=n ` .
27+
28+ - Fix a case where ` esp_http_client_cleanup() ` was not called in certain
29+ scenarios (for example, if the access point is connected, but there is no
30+ outside internet access), which resulted in a memory leak. Thanks to
31+ @mykmelez for providing the fix in
32+ [ #71 ] ( https://github.com/memfault/memfault-firmware-sdk/pull/71 ) 🎉!
33+
34+ - Zephyr:
35+
36+ - Fix a bug in ` memfault_zephyr_port_post_data_return_size() ` where a positive
37+ value could be returned in the event of a failure instead of a negative
38+ value. This would result in ` mflt post_chunks ` returning a successful post
39+ message even though there was a failure such as a DNS lookup failure.
40+
41+ - Add the temperature metric ` cpu_temp ` which is measured using an internal
42+ temperature sensor that some Zephyr boards have. Similar to ESP-IDF, this
43+ metric is collected by default with the Kconfig
44+ ` CONFIG_MEMFAULT_METRICS_CPU_TEMP=y ` , but the board must have the device
45+ tree node ` die-temp0 ` for this option to be used.
46+
47+ - Add an example for collecting thread stack usage metrics when the thread
48+ handles are not accessible in the desired scope. Users can leverage the
49+ Zephyr routine ` k_thread_foreach() ` to register a callback that will be
50+ called with each thread's ` k_thread ` handle. In the callback, users can read
51+ the stack usage via the handle and set their metrics.
52+
53+ ### :boom : Breaking Changes
54+
55+ - Zephyr:
56+
57+ - Change the error return value for
58+ ` memfault_zephyr_port_http_upload_sdk_data() ` to a negative value instead
59+ of 1. This change aligns with the error return value for the other Zephyr
60+ HTTP client APIs, and simplifies logic in the HTTP client.
61+
962## [ 1.9.1] - 2024-05-21
1063
1164### :chart_with_upwards_trend : Improvements
0 commit comments