-
Notifications
You must be signed in to change notification settings - Fork 182
Description
Following the discussion in #4480, I think we should update matio in MSL 4.1.0 to the latest version, to avoid shipping a library with known vulnerabilities. The latest version of matio merged into MSL 4.1.0 was 1.5.24, November last year.
MSL 4.1.0 misses the two latest updates, 1.5.26, which was merged on master on March 28 in #4285 but not back-ported to main/4.1.x, and 1.5.27. If we merge them on maint/4.1.x, we should also re-build the matio binary, since we agreed to still ship the binaries with the MSL for 4.1.0.
Considering the delay in releasing 4.1.0, due to the awkward regression testing process, I think there's no reason to not include them in the 4.1.0 release. We are still not done with regression testing, and the likelyhood that this update introduces some new regressions is very small, so that's not going to be disruptive.
@beutlich what do you think? Could you prepare a PR which updates matio and the matio binaries to 1.5.27 on maint/4.1.x?
If we see that it causes regressions, we can always roll it back.