Renovate unable to update rails

[cswilliams]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Mend Renovate hosted app on github.com

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

Github

Please tell us more about your question or problem

Using the following renovate config:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:recommended",
    "group:allNonMajor"
  ],
  "schedule": [
    "every weekend"
  ],
  "commitMessagePrefix": "chore(deps): ",
  "packageRules": [
    {
      "packageNames": [
        "redis",
        "postgres",
        "internal-gem-1",
        "internal-gem-2",
        "internal-gem-3"
      ],
      "enabled": false
    }
  ],
  "hostRules": [
    {
      "hostType": "rubygems",
      "matchHost": "https://github.com/my-org",
      "encrypted": {
        "token": "REDACTED"
      }
    }
  ]
}

Renovate opens a PR to try to update our rails version from 7.1 to 7.2 and encounters the following artifact error:

Fetching gem metadata from https://rubygems.org/........

rails is locked to 7.1.3.4, while Gemfile is requesting rails (~> 7.2.0, >=
7.2.0). --strict --patch was specified, but there are no patch level upgrades
from 7.1.3.4 satisfying rails (~> 7.2.0, >= 7.2.0), so version solving has
failed

I see in the branch Renovate is changing our Gemfile line from:
gem 'rails', '~> 7.1.3', '>= 7.1.3.2'
to
gem 'rails', '~> 7.2.0', '>= 7.2.0'

When I check out the renovate branch and run bundle install, bundle installs the new rails without error, so this must have something to do with the --strict --patch being specified. Indeed if I check out the branch and run bundle update rails --strict --patch, I get the same error.

Is there a way to get renovate to update our rails without this error? I tried specifying "rangeStrategy": "update-lockfile" in the config but that did not help.

Logs (if relevant)

Logs

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

[cswilliams]

I wonder if this might be a bug. It seemed like renovate should be running the bundle update command with --minor and not --patch. Even the update table in the PR indicates this is a minor update for rails and not a patch update, but for some reason renovate is passing the --patch flag. I will add that since this PR is part of a group update, it includes patch level updates of other gems, so maybe that is throwing it off.

[cswilliams]

I was just looking at the debug logs and this is the bundle command it's running that throws the error:

    "message": "Command failed: bundler lock --patch --strict --update activeadmin rspec-rails sidekiq sprockets-rails stimulus-rails\nrails is locked to 7.1.3.4, while Gemfile is requesting rails (~> 7.2.0, >=\n7.2.0). --strict --patch was specified, but there are no patch level upgrades\nfrom 7.1.3.4 satisfying rails (~> 7.2.0, >= 7.2.0), so version solving has\nfailed\n",
    "stack": "ExecError: Command failed: bundler lock --patch --strict --update activeadmin rspec-rails sidekiq sprockets-rails stimulus-rails\nrails is locked to 7.1.3.4, while Gemfile is requesting rails (~> 7.2.0, >=\n7.2.0). --strict --patch was specified, but there are no patch level upgrades\nfrom 7.1.3.4 satisfying rails (~> 7.2.0, >= 7.2.0), so version solving has\nfailed\n\n    at ChildProcess.<anonymous> (/usr/local/renovate/lib/util/exec/common.ts:99:11)\n    at ChildProcess.emit (node:events:531:35)\n    at ChildProcess.emit (node:domain:488:12)\n    at Process.ChildProcess._handle.onexit (node:internal/child_process:294:12)"
  }

I guess there seems to be some bug around it grouping patch level updates of other gems that depend on rails in the same PR with the rails update.

[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.

Good luck,

The Renovate team