Version 0.2.5 updates

Author: iotblackbelt

Release_notes.md

@@ -15,4 +15,9 @@
     - Automatic response on desired property changes for IoT Central and PnP devices has been removed. It is up to the flow-logic in Node-Red to confirm receipt. The change has been made because the logic in Node-Red should determine whether action is taken based on desired property updates. Similar to the command (direct method) approach. Examples of root and component the confirmation messages are added to the [use](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/blob/master/USE.md) document.
     - Documentation: 
         - CONFIGURE.md added: "Currently only CA based X.509 (group) certificates are supported. Individual device certificates are not. Both individual and group SAS Keys are supported."
-        - USE.md added: description of "Azure IoT Central and PnP require a specific reported property"
+        - USE.md added: description of "Azure IoT Central and PnP require a specific reported property"
+
+## Release 0.2.5:
+- Bug fixes:
+    - [#27](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/issues/27): Incorrect azure-iot-device-amqp version in 0.2.4?
+        - Wrong version in package.json, has been fixed

package.json

@@ -1,7 +1,7 @@
 {
   "name": "node-red-contrib-azure-iot-device",
   "description": "Node-RED node to connect to the Azure IoT platform as a device.",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/iotblackbelt/node-red-contrib-azure-iot-device.git"
@@ -14,8 +14,8 @@
     "node": ">=0.10.0"
   },
   "dependencies": {
-    "azure-iot-device": "^1.15.4",
-    "azure-iot-device-amqp": "^1.15.4",
+    "azure-iot-device": "^1.17.8",
+    "azure-iot-device-amqp": "^1.13.8",
     "azure-iot-device-mqtt": "^1.15.8",
     "azure-iot-provisioning-device": "^1.8.12",
     "azure-iot-provisioning-device-mqtt": "^1.7.12",