Add transformVersion to complement extractVersion

[rarkins]

Tell us more.

Related discussions:

• different versioning schemes in datasource and local git #23276
• Unable to make Renovate to report new GitHub release assets #31249

There are times when a datasource's version string is similar but different to the string in the repo. For example 1.2.3 versus 1-2-3. We could use a versioning like regex to extract major/minor/patch from both of these, but if 1-2-4 were available then the string 1.2.3 in the repo would be replaced with 1-2-4 instead of 1.2.4.

I propose a new config term transformVersion to be used optionally with extractVersion where:

• All named capture groups from extractVersion are made available to transformVersion (maybe handlebars template syntax instead of regex syntax?)
• The full string result of transformVersion would be the version result which is used (no capture group necessary)

We could also potentially use different names for clarity, e.g. extractDatasourceVersion and transformDatasourceVersion, which hopefully are more clear that they apply to the datasource lookup only and not elsewhere in Renovate.

Alternatively we could combine these into a single config option, considering that transforming can't exist on its own anyway:

• New option name is transformDatasourceVersion
• It's an array of strings, with length 1 or 2
• If length 1, it must contain a version capture group
• If length 2, the second element is the "transform" part
• We migrate any existing extractVersion string to be an array of length 1 for transformDatasourceVersion

[mvgadagi]

Hello @rarkins

Regarding the discussion here : #31578
The new configuration would more look like this, could you please have a look?
I am happy to contribute on this feature, so wanted to confirm before I make my hands dirty :)

"transformDatasourceVersion" : ["regex:^(?<major>\\d+)(-|\\.)(?<minor>\\d+)(-|\\.)(?<patch>\\d+)(-|\\.)(?<build>\\d+)$","{{{replace '.' '-' newValue}}}"] 

Thanks a lot in advance :)

[mvgadagi]

Hello @rarkins could you please have a look at this and share your thoughts on this.
Thank a lot ..

[rarkins]

@mvgadagi no, that's not how I had intended it.

You seem to have used a regex versioning template in the first place, which is wrong. In your simple example, it could be something like this:

"transformDatasourceVersion" : ["^(?<datasourceVersion>.*)$","{{{replace '.' '-' datasourceVersion}}}"] 

i.e.

• capture full string in first step, call it datasourceVersion
• Use that captured datasourceVersion in the second step, replacing all . with -

A slightly more advanced version would be like this, allowing for an optional v prefix (which would be stripped):

"transformDatasourceVersion" : ["^v?(?<datasourceVersion>.*)$","{{{replace '.' '-' datasourceVersion}}}"]