Forcing the next version to be a (patch|minor|major) release always uses the highest existing tag #1392
Description
Question
When running the version command on a hotfix branch, the new version is based on the tags in the hotfix branch's history. This is expected and what I want.
But when doing the same with --patch, the new version is a patch increase of the highest tag in the repo.
In the log attached below, this gives 1.4.1 as the new version.
Is this expected behavior?
Configuration
Semantic Release Configuration
[tool.semantic_release.branches.main]
match = "(main|master)"
prerelease_token = "rc"
prerelease = false
[tool.semantic_release.branches.hotfix]
match = "hotfix/*"
prerelease_token = "rc"
prerelease = falseAdditional context
git log --oneline --decorate --graph --all -n 50
* 8e7a550 (HEAD -> hotfix/v1.2.0, tag: v1.2.1) 1.2.1
* 12db328 fix: random stuff
| * d197f21 (tag: v1.4.0, main) 1.4.0
| * bfec9e6 (tag: v1.3.0) 1.3.0
|/
* cc0ce51 (tag: v1.2.0) 1.2.0
* 3fd623e (tag: v1.1.2) 1.1.2
* 172b8e0 (tag: v1.1.1) 1.1.1
* 433ecf4 fix: random stuff
* 12a4459 (tag: v1.1.0) 1.1.0
* a4ffee4 feat: random stuff
* 0a7c5eb random stuff
* 5817fbd (tag: v1.0.0) 1.0.0
* 027d9c3 Add default PSR config to pyproject.toml
* 88cd67e Add python-semantic-release as dependency
* aca2c9f Initial commit