renovatebot / renovate

Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
https://mend.io/renovate
GNU Affero General Public License v3.0
16.52k stars 2.12k forks source link

Support bumpVersion for lockfile-only updates #21996

Open rarkins opened 1 year ago

rarkins commented 1 year ago

What would you like Renovate to be able to do?

Support bumpVersion for the package file even if the only update in the PR is to the lock file.

Per discussion in https://github.com/renovatebot/renovate/discussions/21972

If you have any ideas on how this should be implemented, please tell us here.

It looks like logic needs to be added somewhere after https://github.com/renovatebot/renovate/blob/4924973e9eb6ed592a94f153096d4db7cf9befb7/lib/workers/repository/update/branch/get-updated.ts#L114

Is this a feature you are interested in implementing yourself?

No

github-actions[bot] commented 1 year ago

Hi there,

Get your issue 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.

To get started, please read our guide on creating a minimal reproduction.

We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

SchroederSteffen commented 1 year ago

Minimal reproduction repository: https://github.com/SchroederSteffen/renovate-bump-version-test#readme

jlarmstrongiv commented 1 year ago

Ahh, this issue explains why the publish CI has been failing on my public repos.

My private repos use rangeStrategy: pin, so it always bumped the package.json file.

timjansenortec commented 4 days ago

bumpVersion also does not work for NuGet if central package management is used, and only Directory.Packages.props is updated. Maybe this should be in a separate issue though?