Release version not correlated to previous Prerelease version

[bencat-sixense]

I have a gitflow as follow:

• PR merged on develop -> prerelease
• develop merged on main -> release

When I create the prerelease version, I get this tag: my-project-name-0.5.0-dev.1
So if I merge this develop into main, I expect to get this: my-project-name-0.5.0
But I get this: my-project-name-0.4.2 (the previous release was my-project-name-0.4.1)

Do I miss something or is it the right behavior ?

This is my current project.json config:

    "release": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "noVerify": true,
        "postTargets": ["my-project-name:docker", "my-project-name:github"],
        "preset": "conventional",
        "push": true,
        "trackDeps": true
      }
    },
    "prerelease": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "noVerify": true,
        "postTargets": ["my-project-name:docker"],
        "preset": "conventional",
        "push": true,
        "preid": "dev",
        "releaseAs": "prerelease",
        "trackDeps": true,
        "skipCommit": true
      }
    },

NOTE: I use the latest v5.1.1 with Nx 16 and Node 18

Thank you !

[bencat-sixense]

Anyone please ?

[edbzn]

It's hard to know what's going on with git flow I cannot help you much but in your position I would look at the last generated tag and check if it's correctly pointing to your main branch, semver uses the last tag to calculate the next version.

[edbzn]

It's hard to know what's going on with git flow I cannot help you much but in your position I would look at the last generated tag and check if it's correctly pointing to your main branch especially after you merged develop into main, semver uses the current tag to calculate the next version.

[kaankoken]

@edbzn I have a similar issue but it is not related to gitflow. you could check it out #817

[jhfrintrop]

I think the problem ist this commit: 7459d8b#diff-75b9477886013beac794751b9469c878ea7b9918d6c2abeaf46a9ebde40f81a6.

After that commit all prerelease tags are filtered out if releaseType isn't set.
And releaseType is releaseAs (https://github.com/jscutlery/semver/blob/main/packages/semver/src/executors/version/index.ts#L89), which means that prerelease tags are only considered if releaseAs is set, which means that you have to specify a fixed increment (major, minor, ...), which means semantic versioning is shut off.

[Cavayman]

Hey there, I’m facing an issue with semantic versioning on my current setup. I’m using semver 2.23.0 with Nx 14, and here’s what’s happening:

I have Tag v1.0.0
After that, I have two feature commits.
When I try to generate a prerelease, it gives me 1.0.1-beta (but I was expecting 1.1.0-beta).
If I generate without the prerelease, it correctly generates 1.1.0.
It seems like this issue might be fixed in a newer version (fingers crossed), but I can't update my versions at the moment.

Could someone help me figure this out?
Maybe @edbzn , you could advise me on what to do here?

Thanks a lot!