Product dependencies in Versions.props must be on the latest patch version for libraries dependencies

[carlossanlop]

Addresses item no. 2 of: #72111

Pending clarification:

• https://www.nuget.org/packages/System.Reflection.MetadataLoadContext/6.0.0
  This PR introduced the entry a few days ago but with an older version than the latest stable released version. Waiting for @radical and/or @lewing for confirmation that we can bump it to the latest stable version, per this comment.

Changed (newer stable version found):

• https://www.nuget.org/packages/System.Memory/4.5.5
• https://www.nuget.org/packages/System.Reflection.Metadata/6.0.1

Unchanged (already in latest stable version):

• https://www.nuget.org/packages/Microsoft.Bcl.AsyncInterfaces/6.0.0
• https://www.nuget.org/packages/Microsoft.Bcl.HashCode/1.1.1
• https://www.nuget.org/packages/Microsoft.Win32.Registry/5.0.0
• https://www.nuget.org/packages/System.Buffers/4.5.1
• https://www.nuget.org/packages/System.Collections.Immutable/6.0.0
• https://www.nuget.org/packages/System.ComponentModel.Annotations/5.0.0
• https://www.nuget.org/packages/System.Data.DataSetExtensions/4.5.0
• https://www.nuget.org/packages/System.Data.SqlClient/4.8.3
• https://www.nuget.org/packages/System.IO.FileSystem.AccessControl/5.0.0
• https://www.nuget.org/packages/System.IO.Pipes.AccessControl/5.0.0
• https://www.nuget.org/packages/System.Numerics.Vectors/4.5.0
• https://www.nuget.org/packages/System.Reflection.Emit/4.7.0
• https://www.nuget.org/packages/System.Reflection.Emit.ILGeneration/4.7.0
• https://www.nuget.org/packages/System.Reflection.Emit.Lightweight/4.7.0
• https://www.nuget.org/packages/System.Runtime.InteropServices.RuntimeInformation/4.3.0
• https://www.nuget.org/packages/System.Security.AccessControl/6.0.0
• https://www.nuget.org/packages/System.Security.Cryptography.Algorithms/4.3.1
• https://www.nuget.org/packages/System.Security.Cryptography.Cng/5.0.0
• https://www.nuget.org/packages/System.Security.Cryptography.OpenSsl/5.0.0
• https://www.nuget.org/packages/System.Security.Principal.Windows/5.0.0
• https://www.nuget.org/packages/System.ServiceModel.Primitives/4.9.0
• https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/6.0.0
• https://www.nuget.org/packages/System.Threading.Tasks.Extensions/4.5.4
• https://www.nuget.org/packages/System.ValueTuple/4.5.0

Ignored:

• StyleCopAnalyzersVersion
• SystemTextJsonVersion
• runtimenativeSystemIOPortsVersion

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Addresses item no. 2 of: #72111

Pending clarification:

• https://www.nuget.org/packages/System.Reflection.MetadataLoadContext/6.0.0
  This PR introduced the entry a few days ago but with an older version than the latest stable released version. I reached out to PR owner to confirm if this number needs to be bumped or not.

Changed (newer stable version found):

• https://www.nuget.org/packages/System.Memory/4.5.5
• https://www.nuget.org/packages/System.Reflection.Metadata/6.0.1

Unchanged (already in latest stable version):

• https://www.nuget.org/packages/Microsoft.Bcl.AsyncInterfaces/6.0.0
• https://www.nuget.org/packages/Microsoft.Bcl.HashCode/1.1.1
• https://www.nuget.org/packages/Microsoft.Win32.Registry/5.0.0
• https://www.nuget.org/packages/System.Buffers/4.5.1
• https://www.nuget.org/packages/System.Collections.Immutable/6.0.0
• https://www.nuget.org/packages/System.ComponentModel.Annotations/5.0.0
• https://www.nuget.org/packages/System.Data.DataSetExtensions/4.5.0
• https://www.nuget.org/packages/System.Data.SqlClient/4.8.3
• https://www.nuget.org/packages/System.IO.FileSystem.AccessControl/5.0.0
• https://www.nuget.org/packages/System.IO.Pipes.AccessControl/5.0.0
• https://www.nuget.org/packages/System.Numerics.Vectors/4.5.0
• https://www.nuget.org/packages/System.Reflection.Emit/4.7.0
• https://www.nuget.org/packages/System.Reflection.Emit.ILGeneration/4.7.0
• https://www.nuget.org/packages/System.Reflection.Emit.Lightweight/4.7.0
• https://www.nuget.org/packages/System.Runtime.InteropServices.RuntimeInformation/4.3.0
• https://www.nuget.org/packages/System.Security.AccessControl/6.0.0
• https://www.nuget.org/packages/System.Security.Cryptography.Algorithms/4.3.1
• https://www.nuget.org/packages/System.Security.Cryptography.Cng/5.0.0
• https://www.nuget.org/packages/System.Security.Cryptography.OpenSsl/5.0.0
• https://www.nuget.org/packages/System.Security.Principal.Windows/5.0.0
• https://www.nuget.org/packages/System.ServiceModel.Primitives/4.9.0
• https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/6.0.0
• https://www.nuget.org/packages/System.Threading.Tasks.Extensions/4.5.4
• https://www.nuget.org/packages/System.ValueTuple/4.5.0

Ignored:

• StyleCopAnalyzersVersion
• SystemTextJsonVersion
• runtimenativeSystemIOPortsVersion

Author:	carlossanlop
Assignees:	carlossanlop
Labels:	area-Infrastructure-libraries
Milestone:	7.0.0

[carlossanlop]

@radical@lambdageek are you ok with bumping the System.Reflection.Metadata.LoadContext package version to the latest stable one? You own the code that could be impacted.

@MichaelSimons merely introduced the package to support source-build, which doesn't really care what version is indicated here, as it ends up overriding the value.

[lambdageek]

@radical@lambdageek are you ok with bumping the System.Reflection.Metadata.LoadContext package version to the latest stable one? You own the code that could be impacted.

@carlossanlop I think that's fine. in the past we've had problems with depending on rolling build versions of out of band packages which led to breakage when our task would run on .NET Framework inside VS msbuild. (see the comment below), but stable versions should be ok, I think

runtime/src/tasks/WasmAppBuilder/WasmAppBuilder.csproj

Lines 23 to 26 in 667c170

	<PackageReferenceInclude="System.Reflection.MetadataLoadContext"Version="$(SystemReflectionMetadataLoadContextVersion)" />
	<!-- When we requested a version that is newer than what comes with Visual Studio version of msbuild, it causes problems with
	running the task from inside VS. Therefore, we are using the moving version only for source-build. -->

[lewing]

Yeah the concern here is that the task continues to work with VS/msbuild

[carlossanlop]

@lewing if I bump the version of the package, how do we verify it is still working with VS/msbuild?

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlossanlop]

@radical any concerns about the wasm CI failures? I'm looking at the rest.

[radical]

re:wasm, can't say for sure yet. I'm having trouble even loading the console logs from the helix test runs.

[radical]

@carlossanlop Can you merge main? It has wasm fixes now.

[carlossanlop]

@radical done.

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlossanlop]

/azp run runtime

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlossanlop]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlossanlop]

This will have to be backported to rc1.

[carlossanlop]

/backport to release/7.0-rc1

[github-actions]

Started backporting to release/7.0-rc1: https://github.com/dotnet/runtime/actions/runs/2870765762