Closed rarkins closed 6 years ago
I suggest we'd call this "bumpVersion" and make it boolean (false by default). We would do this manually rather than actually running "npm version patch".
Perhaps "bumpVersion" and default to "none" but allow "patch" or "minor" as values.
Waiting on #1016, otherwise it's hard to make sure we don't accidentally bump it twice if branch is updated with second commit.
@rarkins think you can move this forward now? :)
@gunar yes, good idea. Nowadays, Renovate always has only one commit per branch, so it makes it much easier.
@gunar now implemented and live in the app, if you'd like to try it out again.
e.g. to bump version every time, just add this to the root of your renovate.json
:
"bumpVersion": true
If you only want it for dependencies
(not devDependencies
), then add this:
"dependencies": {
"bumpVersion": true
}
@rarkins you are awesome! will try asap.
@rarkins I'd like to quickly ask about bumpVersion
. It seems like the setting "bumpVersion": "patch"
is ignored if the major version is 0, but works for numbers greater than 0. Is this an intended behaviour?
Not intended. Could you raise a bug report?
@rarkins Apparently the issue resolved all of a sudden, but I stumbled upon another issue I will raise a bug report for when I am able to recreate it.
As suggested by @gunar on twitter, this would see Renovate bump the version in
package.json
.