.NET 6 issue with System.Text.Json 7.0

Where can we find the TeeChart .NET build that utilizes System.Text.Json 6.0? We are running into the issue below:

Warning MSB3277 Found conflicts between different versions of "System.Text.Json" that could not be resolved.
There was a conflict between "System.Text.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" and "System.Text.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51".
"System.Text.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was chosen because it was primary and "System.Text.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was not.
References which depend on "System.Text.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [C:\Users\user\.nuget\packages\microsoft.netcore.app.ref\6.0.29\ref\net6.0\System.Text.Json.dll].
C:\Users\user\.nuget\packages\microsoft.netcore.app.ref\6.0.29\ref\net6.0\System.Text.Json.dll
Project file item includes which caused reference "C:\Users\user\.nuget\packages\microsoft.netcore.app.ref\6.0.29\ref\net6.0\System.Text.Json.dll".
C:\Users\user\.nuget\packages\microsoft.netcore.app.ref\6.0.29\ref/net6.0/System.Text.Json.dll
References which depend on or have been unified to "System.Text.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [].
C:\dev\LynxNext\Lynx\Solution\ThirdParty\bin\TeeChart.dll
Project file item includes which caused reference "C:\dev\LynxNext\Lynx\Solution\ThirdParty\bin\TeeChart.dll".
ToroChart
C:\dev\LynxNext\Lynx\Solution\ThirdParty\bin\TeeChart.WinForm.dll
Project file item includes which caused reference "C:\dev\LynxNext\Lynx\Solution\ThirdParty\bin\TeeChart.WinForm.dll".
ToroChart DailyOperation C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets 2389

[Marc]

Hello,

Please confirm that you are working with the latest TeeChart build, 4.2024.4.20, (see https://www.nuget.org/packages/Steema.T ... .2024.4.20).

With thanks.
Regards,
Marc Meumann