Merge pull request #89 from sorru94/prepare-0.7.0

Prepare release v0.7.0

Author: harlem88

CHANGELOG.md

@@ -9,6 +9,39 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.1.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## [0.7.0] - 2024-12-19
+### Added
+- The function `edgehog_device_stop` that allows stopping the Edgehog device. Including the
+  telemetry services.
+- The result value `EDGEHOG_RESULT_TELEMETRY_STOP_TIMEOUT`. This is returned when Edgehog failed
+  to stop within the user defined timeout.
+- The public definition of the zbus channel `edgehog_ota_chan`. That can be used to interact with
+  the Edgehog device during OTA updates.
+- The zbus event `EDGEHOG_OTA_PENDING_REBOOT_EVENT`. This event is sent by the Edgehog device on
+  the zbus when an OTA has been received, correctly flashed in the secondary partition, and the
+  device is ready for a reboot.
+- The zbus event `EDGEHOG_OTA_CONFIRM_REBOOT_EVENT`. This event can be used to reply to a
+  `EDGEHOG_OTA_PENDING_REBOOT_EVENT` triggering an immediate reboot of the device, skipping the
+  usual wait time that the Edgehog device uses for the reboot.
+- Support for Zephyr `4.0` for the sample.
+- The `stm32h573i_dk` board into the standard boards for the sample.
+- A new readme for the sample specific for the NXP Application Hub.
+
+### Changed
+- `edgehog_device_telemetry_config_t` has been renamed to `edgehog_telemetry_config_t` to be
+  coherent with the library naming scheme.
+- `telemetry_type_t` has been renamed to `edgehog_telemetry_type_t` to be coherent with the library
+  naming scheme.
+- The sample has been reorganized to be easier to understand.
+- The Astarte device has been updated to the latest `0.7` version.
+
+### Removed
+- The WiFi driver in the sample. Currently no board with WiFi is included in the standard
+  boards for the Edgehog sample.
+
+### Fixed
+- Prevent illegal memory acces in the function `edgehog_telemetry_destroy`.
+
 ## [0.6.0] - 2024-09-12
 ### Added
 - Add support for `io.edgehog.devicemanager.SystemStatus` interface.

README.md

@@ -51,7 +51,7 @@ Second, a new entry should be added to the projects list:
       remote: edgehog-device-manager
       repo-path: edgehog-zephyr-device.git
       path: edgehog-zephyr-device
-      revision: v0.6.0
+      revision: v0.7.0
 ```
 Remember to run `west update` after performing changes to the manifest file.
 

doc/CMakeLists.txt

@@ -7,7 +7,7 @@ project(Edgehog-Device-Doc LANGUAGES)
 
 set(MIN_WEST_VERSION 1.0.0)
 
-set(Edgehog_Device_VERSION 0.6.0)
+set(Edgehog_Device_VERSION 0.7.0)
 
 message(STATUS "Zephyr base: ${EDGEHOG_DEVICE_BASE}")
 message(STATUS "Documentation tag: ${DOC_TAG}")

include/edgehog_device/device.h

@@ -28,7 +28,7 @@
 /** @brief Major version number */
 #define EDGEHOG_DEVICE_MAJOR 0
 /** @brief Minor version number */
-#define EDGEHOG_DEVICE_MINOR 6
+#define EDGEHOG_DEVICE_MINOR 7
 /** @brief Patch version number */
 #define EDGEHOG_DEVICE_PATCH 0
 

samples/edgehog_app/README_NXP.md

@@ -41,7 +41,7 @@ installed, this can be done through the
 
 The application demonstrates the use of the
 [Edgehog device for Zephyr](https://github.com/edgehog-device-manager/edgehog-zephyr-device) at
-version **0.6.0**.
+version **0.7.0**.
 
 Every Edgehog device relies internally on the [Astarte](https://docs.astarte-platform.org/) plaftorm
 to enable remote communication. In this application we will rely on the