What versions of CoreCLR are compatible with each other?

Question

.NET

Question out of curiosity.
According to different versions of the .NET Framework, there was good version compatibility with each other. As a rule, simple programs could work on neighboring versions of the framework if the CLR version matched. And, accordingly, the version of the IL language in EXE / DLL files. The same is about using other people's assemblies, originally assembled for the next version of the framework.

CLR 1.0 = .NET FW 1.0
CLR 1.1 = .NET FW 1.1
CLR 2.0 = .NET FW 2.0, 3.0, 3.5
CLR 4.0 = .NET FW 4.0, 4.5.x, 4.6.x, 4.7.x, 4.8.x

Accordingly, a program compiled under FW 4.8 without using the functions that appeared after FW 4.0 could easily work on WinXP. For example. And 10-year-old DLLs written in Visual Studio 2010 are easily connected to .NET FW 4.8 projects (unlike DLLs for .NET FW 2.0/3.5, which no longer want to).

It became interesting, but what about .NET Core? Google didn't find much information. What is there in terms of compatibility between, say, .NET Core 3.1 and .NET Core 3.0 in both directions? Or 2.0 and 2.1, 2.1 and 3.1....?

Code compatibility is, in general, easily visible on MSDN. But nothing is clear about the launch of binaries.

Answer 1

The .NET Standard describes a set of APIs for various versions.