Feedback wanted: Renovate's monorepo support

[jamietanna]

We (the Renovate maintainers) are seeking community feedback on how Renovate makes updates to monorepos.

We're looking to understand:

• how you're using Renovate
• what package ecosystems you're using
• what difficulties you find with working on a large monorepo
• what workarounds you've put in place for these, if any
• what you find works well with Renovate's monorepo functionality?
• how long does Renovate take to run against the monorepo? (look for the Repository finished log message at the end of the run)

In-scope:

• Users of Git repos which are a monorepo (at whatever scale you're using them)
• Ideally multi-team monorepos
• Ideally multi-language/multi-tooling monorepos
  • Which is ??, but it's worth being explicit!

Out-of-scope:

• How Renovate supports PR updates to external monorepos i.e. via group:monorepos

Template:

Our monorepo requires:

- [ ] Dependencies (i.e. `node`, `github.com/google/uuid`) <!-- delete as appropriate --> **must be**/**do not have to be** in-sync across all modules in the monorepo
- [ ] Human review for all dependency updates
- [ ] Specific monorepo tooling that Renovate <!-- delete as appropriate --> **does**/**does not** support

I am a (select multiple if appropriate):

- [ ] user
- [ ] person in a security-focussed role
- [ ] person in a legal-focussed role
- [ ] self-hosted administrator

<!-- Ideally, run `jq '.config | to_entries | map({manager: .key, total: ([.value[].deps | length] | add)})'` against the `packageFiles with updates` log line (Co-authored-by: Claude Sonnet 4.5 (GitHub Copilot)) -->
Package ecosystems we're using: <!-- does not need to be exhaustive, but it's good to have a rough idea of what you're using -->

Number of branches we manage: <!-- this will be 1, or the number of branches matched by https://docs.renovatebot.com/configuration-options/#basebranchpatterns -->

Positives of Renovate's monorepo support:

- <!-- add as appropriate -->

Negatives of Renovate's monorepo support:

- <!-- add as appropriate -->

Workarounds / config hacks we've found to work really well:

- <!-- add as appropriate -->

Length of last Renovate run: <!-- look for the `Repository finished` log message at the end of the run -->

Additional feedback:

[izorg]

Our monorepo requires:

• Dependencies (i.e. node, github.com/google/uuid) must be in-sync across all modules in the monorepo
• Human review for all dependency updates

I am a (select multiple if appropriate):

• user
• person in a security-focussed role
• person in a legal-focussed role
• self-hosted administrator

Package ecosystems we're using: npm , docker, github-actions

Number of branches we manage: 1

Positives of Renovate's monorepo support:

Works perfect

Length of last Renovate run: 58 s

Additional feedback:

Thank you very much for your effort

[Kakadus]

I have basically the same requirements / experience here. Renovate works okay-ish for us, but we run into #40474 with our npm monorepo.

Our monorepo requires:

• Dependencies (i.e. node, github.com/google/uuid) must be in-sync across all modules in the monorepo
• Human review for all dependency updates

I am a (select multiple if appropriate):

• user
• person in a security-focussed role
• person in a legal-focussed role

Package ecosystems we're using: npm, docker, github-actions

Number of branches we manage: 1

Positives of Renovate's monorepo support:

• works okay-ish. We get some updates

Negatives of Renovate's monorepo support:

• some packages aren't updated. Manual intervention needed.
• monorepo packages are not able to be looked up by renovate (Failed to look up npm package @workspace/package: no-result). We explicitly ignore those packages.

Length of last Renovate run: 1m 18s

Thanks a lot.