Squash merging breaks versioning without warning or documentation about semver HOT 5 OPEN

Exact same problem. I recently migrated from semantic-release. It worked without a problem there but with semver squash-merging produces the above issue.

from semver.

That is the only bigger difference I see in two different PRs where one worked and the other failed.
The setup is a monorepo with different packages that get released. The release is triggered each time a PR is merged into the develop branch through github actions.

from semver.

Ok so I found what is the cause on my side. So GitHub actions can run concurrently which means that while one is still in progress with incrementing the version and release the other will start and do a git checkout which will pull the code that does not contain the new version tags yet. Which causes it to fail when the first action generates new tags that now conflict with the second action run. This issue gets amplified in case the jobs are doing other stuff in between which makes it more likely that another job will start running in between.
Now the solution here would probably be concurrency setting for GitHub actions

UPDATE: the concurrency did not work for me. Might be doing something wrong.

from semver.

Well, squash merging shouldn't produce any problem as far as you release your main branch. I would need more detail on your workflow to have an idea about the underlying issue.

from semver.

@edbzn It seems like versioning as it's implemented here shouldn't be tied to a specific workflow, it should be flexible to fit in wouldn't you agree? The current implementation seems to imply that in order to use this plugin, specific instructions on workflow should be provided? My setup is almost the same as @nejcm describes above.

That is the only bigger difference I see in two different PRs where one worked and the other failed.
The setup is a monorepo with different packages that get released. The release is triggered each time a PR is merged into the develop branch through github actions.

I am running into almost the exact same issues he describes in the comment before this one.

from semver.