iOS `buildNumber` is parsed as number

[DavidStrausz]

The following commit introduced forced number parsing:
ba5f8f2

This is breaking and causes incorrect build numbers for projects that use build numbers that are in sync with the version (e.g. 1.0.0) instead of incrementing an integer (in this case 1.0.0 would be parsed as 1).

[mlynch]

Okay I'll need to go back to the drawing board with this one, thanks for the heads up

[mlynch]

@DavidStrausz what would you expect to happen here? Nothing, or semver increment?

[DavidStrausz]

@mlynch Nothing I'd say, any logic regarding build numbers and other values should be handled by ci/cd scripts (e.g. faslane), and trapeze just applies the values set in config.yaml/env vars

[mlynch]

Ah nevermind, you aren't using this with increment. I got it

[mlynch]

Fixed in 7.0.8. Also fwiw Android versionCode only supports integers, so this fix was just for iOS

[DavidStrausz]

I just updated and it's working as expected again! And yes you are right about the Android versionCode property.
Thank you, and great package btw! :)