possible to auto-increment patch version, similar to what npm version / yarn version does?

[vesper8]

I really like how npm version patch / yarn version --patch works. It will auto-increment 1.1.18 to 1.1.19 for example

It follows semver and these are just some of the methods it supports:

    --new-version [version]             new version
    --major                             auto-increment major version number
    --minor                             auto-increment minor version number
    --patch                             auto-increment patch version number
    --premajor                          auto-increment premajor version number
    --preminor                          auto-increment preminor version number
    --prepatch                          auto-increment prepatch version number
    --prerelease                        auto-increment prerelease version number

It would be lovely if this package could integrate this kind of functionality.

I am most interested in just being able to auto-increment the patch number

Many thanks

[gligoran]

Hi @vesper8, an interesting idea.

I'm a bit hesitant to implement such a feature as it adds an opinionated view on how the version should increase.

cordova-set-version can pull the version from your package.json, if you have one. To get it to do that you need to call it without the version and the buildNumber arguments. Would that workflow work for you?

[vesper8]

It wouldn't because I actually have a different version in my package.json than in my config.xml for a reason. I use Microsoft CodePush so every time I do a code push I increment the package.json version which I then reference inside my app, but I only increment the config.xml version when I distribute a new release to the App Store.

The way that yarn/npm handles it is very flexible and not opionated but I understand it would be more work to implement, but it gives you the full flexibility of specifying what kind of version increment you want to produce.

I agree that not passing a value to -b should not just automatically assume that you want to increment the patch version IE 1.0.2 to 1.0.3

Ideally you would leave the -b flag as is and introduce a few new flags such as --patch, --minor and --major, and when those are passed to the CLI they would auto-increment respectively. So --patch would increment 1.0.2 to 1.0.3, --minor would increment 1.0.2 to 1.1.0 and --major would increment 1.0.2 to 2.0.0

That would be very helpful!!

[gligoran]

I agree that not passing a value to -b should not just automatically assume that you want to increment the patch version IE 1.0.2 to 1.0.3

Ideally you would leave the -b flag as is and introduce a few new flags such as --patch, --minor and --major, and when those are passed to the CLI they would auto-increment respectively. So --patch would increment 1.0.2 to 1.0.3, --minor would increment 1.0.2 to 1.1.0 and --major would increment 1.0.2 to 2.0.0

I think there was a misunderstanding about the -b/buildNumber. I didn't mention anything about incrementing the version if you don't pass it. The way cordova-set-version works at the moment is that it reads the version in package.json if you don't pass it either the version or the buildNumber argument.

It wouldn't because I actually have a different version in my package.json than in my config.xml for a reason. I use Microsoft CodePush so every time I do a code push I increment the package.json version which I then reference inside my app, but I only increment the config.xml version when I distribute a new release to the App Store.

The way that yarn/npm handles it is very flexible and not opionated but I understand it would be more work to implement, but it gives you the full flexibility of specifying what kind of version increment you want to produce.

Why I say adding semver style version incrementing is opinionated is because I can't find other specification of what the version attribute holds in config.xml than "Full version number expressed in major/minor/patch notation." Although it says for plugin.xml that "A version number for the plugin. Semver syntax is supported.". And if version in config.xml is not purely semver, then adding semver-style increment functionality would impose an opinion on how the version should be incremented.

If version in config.xml does supports full semver, then I'd gladly add the semver-style increments.

Unfortunately I don't have cordova set up on my machine at the moment, so would you be able to test if version supports just major.minor.patch or does it support full semver? Example values to test would be 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85, 1.0.0+21AF26D3----117B344092BD, 0.2.0-beta.2, 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.-.

[vesper8]

It does not support full semver, only major, minor and patch notation. This is written here https://cordova.apache.org/docs/en/latest/config_ref/index.html#widget

When I tried some of your examples I either got a version parse failed error (1.0.0+20130313144700) or I got an error while trying to submit my release to Apple (1.0.0-alpha)

It would be great if you could add the functionality as I described in my previous message for --patch, --minor and --major. Everything else could remain the same and this would just be an extra for those who wish to use it.

Let me know if there's anything else I can assist with. Thanks!

[gligoran]

Thanks for the test. I'm working on some further changes to tests, which will allow me to add more features more easily. It's probably going to take a bit of time, as this is a hobby project, though.

[vesper8]

@gligoran any update to this auto-incrementing ability? I thought your latest release might include it but it seems not

[gligoran]

@gligoran any update to this auto-incrementing ability? I thought your latest release might include it but it seems not

Hey, sorry for the late reply. I'm swamped at the moment so it's hard to find time to work on this. I'm doing a rewrite of how tests work to make it easier to add things like this, but it's slow work. I'll post an update once I make some progress.