Coreclr is out of date

I was able to deduce that Aspose.Cells for Python via .NET is using dotnet/coreclr version 3.1. That repository was merged into dotnet/runtime years ago, and the last release is over two years old. The newer dotnet/runtime supports openssl 3, while dotnet/coreclr supports the older – and vulnerable – openssl 1.1.

There are many years-old support requests related to the old openssl libraries that have yet to be resolved. And I am also seeing issues loading ICU (libicu*) versions > 70 without setting the CLR_ICU_VERSION_OVERRIDE environment variable or installing a legacy library.

We are interested in renewing our Aspose.Cells Product Family license, but we need to know that Aspose is going to continue to stay on top of library updates so that we can be sure our products using Aspose.cells will work on the latest Linux, macOS, and Windows versions, and that fixes for known vulnerabilities are being and will continue to be addressed.

What is the timeline for moving Aspose.Cells from the legacy dotnet/coreclr codebase to the newer dotnet/runtime code?

This information will help my team as we evaluate a license renewal.

Thank you.

@brandon.avantus

Can you please specify what specific information or timeline you are looking for regarding the transition from dotnet/coreclr to dotnet/runtime for Aspose.Cells?

@brandon.avantus
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSPYTHONNET-247

We will investigate this issue as soon as possible.