Skip to content

Renovate updates should manage updates across submodules (OSOE-1190) #1167

@Piedone

Description

@Piedone

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.
  • This frequently plagues xUnit updates as well.
  • This is just for OSOE.
  • We need to do this after Create our own .NET SDKs (OSOE-1208) #1190, because that might make this largely unnecessary.

Jira issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions