Versioning, PR Build has larger version number than CI/CD

[navdotnetreqs]

Hi,

I'm wondering about the correct way to address this issue.

• PR build for my branch created an app.file with version 1.0.2147483647.1
  -> I installed this to a sandbox, tested, all is good

• when I squash merge the PR, the CI/CD is run, creating app file 1.0.2.0
  -> I cannot install this into the same sandbox, since the version is less than the PR build

This is probably due to the default strategy using runNumber for the workflow, and I guess that's workflow specific (CI/CD vs. PR Build)?

Are my only options to:

1. use date&time for the versioningStrategy (2)
2. Increase the versions (how, automatically?) before the merge

Is there a better way?

[navdotnetreqs]

I tried this, it looks like versioningStrategy doesn't affect the version of the app in the PR build?

I got version 1.0.2147483647.1. What is this and how do I control it ?

..and why is it max integer?

[navdotnetreqs]

So, for future generations, as a hack, one can edit _BuildALGoProject.yaml

and after
-name: Read settings
add

- name: Override appBuild for PR versioningStrategy 15
     shell: pwsh
     run: |
       $settings = $env:Settings | ConvertFrom-Json -Depth 99
       if ($settings.versioningStrategy -eq 15) {
           Write-Host "Overriding appBuild from $($settings.appBuild) to 0"
...