-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to LTS_07_2021_Ref01 (CA-167) #122
Comments
@mahavirj Do you know, if it is prioritised? |
@MartinTJDK There isn't plan for update to LTS_07_2021_Ref01? What new functions for your project need update it? |
@lhespress LTS_07_2021_Ref01 has several bugfixes, which we need. |
@mahavirj @MartinTJDK @lhespress I think this repo needs LTS_07_2021_Ref01. |
@epictrave I agree. The certificate bundle has to be updated. But it would also be nice to get bugfixes as well. |
@mahavirj @lhespress Is it something you will consider? |
@MartinTJDK As mentioned earlier, no updates are planned in the near future, we are discussing which to update because of there are both Azure-iot-SDK-C and Azure-SDK-for-c to access Azure-IoT. |
@lhespress I'm not sure this has been stated clearly enough by @epictrave so I'll just stress it again here: without this LTS, the source code will not contain the right CA for ESP32 devices to be able to connect to azure anymore, as explained in this blog post. So getting this update, if not for all the other stability fixes, doesn't seem like optional for people using this repo when building their binaries for ESP devices connecting to azure. If it's not officially upgraded, we will have to upgrade ourselves one way or another, or devices will not be able to connect to azure anymore (and that will happen soon). |
@matgardon We have create a merge request for update it to LTS_01_2022_Ref01 and will release it after review finish. |
@lhespress awesome news, thanks for the follow up 🙏 |
This has now been pushed out to the repository. |
Any plans for update to LTS_07_2021_Ref01?
The text was updated successfully, but these errors were encountered: