Issue with updateVersionNumber After Creating a Release Using AL-Go Action

[CITPhilipp]

After creating a release using the AL-Go action "Create Release", I encountered the following error:
updateVersionNumber is '0.0.1', must be a version number with 2 segments or one of: +1, +0.1

It seems that the updateVersionNumber is not in the expected format. However, I'm unable to create a new release because it's not allowed to create a second release on the same commit.
Is there a way to change the updateVersionNumber after the release has been created, or is there a recommended workaround for this situation?

[aholstrup1]

So, the release was created successfully but the workflow failed when it was trying to update version numbers? If that's the case, you can increment the version numbers with the "Increment Version Number" workflow.

Which version of AL-Go are you running?

[CITPhilipp]

Thanks for your response.

I'm currently using AL-Go version 7.2.
I tried the workaround you suggested, but I'm still encountering the same error when attempting to increment the third position of the version number.
My attempt was to use +0.0.1, but it didn’t resolve the issue.

Error Message:
Unexpected error when running action. Error Message: updateVersionNumber is '+0.0.1', must be a version number with 2 segments or one of: +1, +0.1, StackTrace: at Validate-UpdateVersionNumber

[aholstrup1]

Depending on your settings this error is likely expected. Did you set the versioningStrategy setting somewhere in your AL-Go settings? If not, try looking in the log for versioningStrategy.

If your versioning strategy is anything else than 3, the build.revision section of the build number (major.minor.build.revision) will be controlled by AL-Go. That's why we throw an error when you try to increment the revision number.

If you want to control the revision number from the app.jsons, you'd need to set your versioningstrategy to 3. If you do, I expect the workflow to succeed.

More information on versioning strategies here:
https://aka.ms/algosettings#VersioningStrategy

[CITPhilipp]

Thanks for your help, and for the workaround using the "Update Version Numbers" action.