Major, Minor and Patch version parts as separate variables

[petersendev]

Hi, additionally to the NBGV_MajorMinorVersion I would really like to have all the version parts available as separate (environment) variables.

Since (as I understand it) the version height doesn't have to be in the patch part of the version, all three would be preferable.

I need this primarily in a cloudbuild (via nbgv cloud -c -a) for docker tags ( 0.x, 0.1.x, 0.1.2), which is currently not possible without parsing the version via script.

I would like to request the feature that nbgv would set NBGV_Major, NBGV_Minor and NBGV_Patch.

As a bonus, the NBGV_PrereleaseVersion without the leading dash would also be welcomed.

[AArnott]

This all sounds reasonable. I'll try to get this done over the next week or so. If someone wants to send a PR, just ping me before working on it so we can avoid double work.

[AArnott]

The properties (excluding the NBGV_ prefix) are:

1. VersionMajor
2. VersionMinor
3. BuildNumber (this was preexisting)
4. VersionRevision

The BuildNumber always represents the 3rd integer in the version. If you want the version/git height specifically, use VersionHeight, since as you say that may not appear as the 3rd integer.

I've also added a PrereleaseVersionNoLeadingHyphen property for you.

[petersendev]

Sounds great, thank you so much!

[petersendev]

Any ETA on a release? Would love to migrate my last projects, but they are blocked by this.

[AArnott]

Done. It's v2.2.33 on nuget.org. If you don't see it yet, check again in an hour.