lockFileMaintenance with baseBranchPatterns: PR created and filed against wrong branches

[tgross35]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

I don't have access, but the PR was created 2026-10-06

Please tell us more about your question or problem

I have a renovate configuration that should run lockFileMaintenance against two separate branches. The default branch (main) works fine. For the other branch, it appears that renovate creates a commit based on top of the default branch, but opens a PR against the other branch.

Example: rust-lang/libc#5499 or rust-lang/libc#5487. Renovate should have checked out libc-0.2, run and committed lockfile updates, then created a PR against libc-0.2. Instead, it looks like it checked out main, ran and committed lockfile updates, then created a PR against libc-0.2.

Relevant bits of config:

{
  $schema: "https://docs.renovatebot.com/renovate-schema.json",
  extends: [
    "config:recommended",
    ":maintainLockFilesMonthly",
    "helpers:pinGitHubActionDigestsToSemver",
  ],
  commitMessagePrefix: "deps:",
  baseBranchPatterns: ["main", "libc-0.2"],
  lockFileMaintenance: {
    enabled: true,
    schedule: ["* * 1-7,15-21 * 1"],
  },
  packageRules: [
    {
      matchCategories: ["rust"],
      matchJsonata: ["isBreaking != true"],
      enabled: false,
    },
    {
      matchCategories: ["rust"],
      addLabels: ["stable-declined"],
    },
  ],
}

Full config at https://github.com/rust-lang/libc/blob/985f26f4685c467dc2939c90c572886aa36a4b38/.github/renovate.json5

Logs (if relevant)

No response

[tgross35]

Oh wow thank you for the quick response! I'll get that going.

I don't have access to the logs unfortunately, asking if somebody on our infra team does.