[Bug]: AL-Go should throw an error or a warning if you create a release, which is older than the latest release

[cegekaJG]

AL-Go version

6.3 (customized)

Describe the issue

A while ago, we had a typo in the tag parameter for the Create new release action, writing 32.9.0 instead of 23.9.0. From that point on forward, all future releases (whose major version number is still well below 32) have been using the tag 32.9.0 to compare with.
I've since deleted the faulty tag and its release, but it could be a problem for certain release strategies.

Expected behavior

When creating the changelog, AL Go should either use the latest tag or tag of the latest release. Alternatively, the workflow could look for the highest version below the version in the tag of the new release.
If it's necessary to use the highest tag version, the workflow should run into an error and inform the user.

Steps to reproduce

• Enter a repository with AL Go
• Create a new release with tag 32.9.0
• Introduce some changes
• Create a new release with tag 25.2.0
• Introduce more changes
• Create a new release with tag 25.2.1

At this point, both releases should use 32.9.0 to compare with.

Additional context (logs, screenshots, etc.)

The customized AL Go repository can be found here.

Additionally, I've attached the log of the Create new release workflow.

logs_36510432474.zip

[freddydk]

It is by design that we use the version numbers for sorting.
I agree that if you create a new release with latest version of the apps in your repo, we should throw an error if the version is lower than the latest version already released.
If you create a new release and specify a specific version of the apps in your repo, we should give a warning.