Renovate creates unexpected major updates

[mkoptelov-xovis]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Azure DevOps, latest vesion

Please tell us more about your question or problem

I want renovate to create only minor and patch updates for my angular project. Here is my config:

module.exports = {
    platform: "azure",
    separateMinorPatch: true,
    
    repositories: [
        "my-repo"
    ],
    hostRules: [
        {
          hostType: 'npm',
          matchHost: 'pkgs.dev.azure.com',
          username: 'apikey',
          password: process.env.RENOVATE_TOKEN,
        },
      ],
    packageRules: [
        {
            groupName: "all minor and patch dependencies",
            groupSlug: "all-minor-patch",
            matchPackageNames: ["*"],
            matchUpdateTypes: ["minor", "patch"]
        },
        {
            groupName: "all major dependencies",
            groupSlug: "all-major",
            matchPackageNames: ["*"],
            matchUpdateTypes: ["major"],
            enabled: false
        },
        {
            groupName: "ignored minor dependencies",
            groupSlug: "ignored-minor",
            matchPackageNames: ["typescript"],
            matchUpdateTypes: ["major", "minor"],
            enabled: false
        }
    ],
    requireConfig: "optional",
    onboarding: false,
    autodiscover: false,
    npmrcMerge: true
}

So the topmost rule is the only enabled, while as majors updates are explicitly disabled. Still, renovate pushes updates like:

Also - how can I close the PR on Azure DevOps so it does not recreated again? If I abandon it - it will reappear the next time I run renovate

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rarkins]

There's no need to add group config when disabling. It likely doesn't cause any problem, but it's superfluous.

Otherwise it's not obvious why major updates aren't disabled so we need a reproduction repo to test against

[medz]

medz/prisma-dart#461 I encountered the same problem. In dart pub, it does not detect whether the entire workspace dependencies are equivalent, and each PR needs to be manually verified.