You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 24, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: Release_notes.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,14 @@
1
1
# Release notes
2
2
3
+
## Release 0.2.6:
4
+
- Updates:
5
+
- Updated to latest version of Azure IOT SDK (1.9.0 for device)
6
+
7
+
## Release 0.2.5:
8
+
- Bug fixes:
9
+
-[#27](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/issues/27): Incorrect azure-iot-device-amqp version in 0.2.4?
10
+
- Wrong version in package.json, has been fixed
11
+
3
12
## Release 0.2.4:
4
13
- Bug fixes:
5
14
-[#26](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/issues/26): Why is SAS key visible in logging bug?
@@ -16,8 +25,3 @@
16
25
- Documentation:
17
26
- 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."
18
27
- USE.md added: description of "Azure IoT Central and PnP require a specific reported property"
19
-
20
-
## Release 0.2.5:
21
-
- Bug fixes:
22
-
-[#27](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/issues/27): Incorrect azure-iot-device-amqp version in 0.2.4?
0 commit comments