You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See e.g. this PR: #1165. It fails because .NET consolidation verification fails due to the submodules not using the same Microsoft.NET.Test.Sdk version. Instead, this PR could include submodule updates including the same Microsoft.NET.Test.Sdk version updates.
This means that we'd have more merges to OSOCE than now if there are both such common package updates and unique ones, but this is not a problem.
Since we have a common Renovate configuration, probably we can rely on branches being the same. In the example this is renovate/non-breaking-dependency-versions. However, at the point of the OSOCE PR being opened, the submodule PRs might not be ready.
Can this be done with Renovate configuration? Or maybe we need a GHA implementation.
See e.g. this PR: #1165. It fails because .NET consolidation verification fails due to the submodules not using the same
Microsoft.NET.Test.Sdkversion. Instead, this PR could include submodule updates including the sameMicrosoft.NET.Test.Sdkversion updates.renovate/non-breaking-dependency-versions. However, at the point of the OSOCE PR being opened, the submodule PRs might not be ready.Jira issue