"Dependabot is rebasing this PR" but nothing happens

[dmke]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Bundler

Package manager version

Bundler 2.4.22, 2.5.6, 2.5.22

Language version

Ruby 2.7-3.3

Manifest location and content before the Dependabot update

• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-6.0/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-6.1/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-7.0/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-7.1/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-7.2/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-8.0/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/gemfiles/rails-main/Gemfile
• https://github.com/digineo/texd-ruby/blob/master/Gemfile

dependabot.yml content

https://github.com/digineo/texd-ruby/blob/master/.github/dependabot.yml

Updated dependency

various

What you expected to see, versus what you actually saw

I have setup Dependabot to inform me about updates.

However in this particular repository, I manually perform updates (through a make target, which creates a squashed commit). Pushing the commit will then trigger the "⚠️ Dependabot is rebasing this PR ⚠️" message, but more often then not nothing happens.

I'd expect Dependabot to detect that the PR has become outdated and close it.

Native package manager behavior

bundle update does what it ought to do, there are is special output.

Images of the diff or a link to the PR, issue, or logs

Most recently:

• build(deps): bump rails from 7.0.8.5 to 7.0.8.6 in /gemfiles/rails-7.0 digineo/texd-ruby#374
• build(deps): bump rails from 7.1.4.1 to 7.1.4.2 in /gemfiles/rails-7.1 digineo/texd-ruby#375
• build(deps): bump rails from 6.1.7.9 to 6.1.7.10 in /gemfiles/rails-6.1 digineo/texd-ruby#376
• build(deps): bump rails from 7.2.1.1 to 7.2.1.2 in /gemfiles/rails-7.2 digineo/texd-ruby#377

(In the meantime, I've closed them manually.)

Smallest manifest that reproduces the issue

No response