Miguel

Hi @gr2m @travi , First of all, thank you for your work in this repo! I only would like to point the attention a bit towards this PR. Of course...

Hi @gr2m. Sorry to bother again. Just wanted to know if there's been any progress in the review of this PR. If you think that I should address it to...

I've encountered the same problem with different versions of **semantic-release**. But I've I discovered that it only happens when you try to publish a new maintenance version from a **maintenance...

What do you think about this issue @gr2m? Is it indeed a bug? I mentioned you, @gr2m, because I saw you've been pretty active managing other issues/PRs/discussions, but if you...

@mrmartan I think in this case, it does not matter if it's a `maintenance branch` or `hotfix branch`, essencially is the same concept and the wrong behavior is present in...

I've made other tests with the configuration and the workflow that are described in the documentation ([maintenance release](https://github.com/semantic-release/semantic-release/blob/0785a844fa8ac1320383452ce531898be3b01f92/docs/recipes/maintenance-releases.md#releasing-a-bug-fix-for-version-10x-users) and [pre-releases](https://github.com/semantic-release/semantic-release/blob/0785a844fa8ac1320383452ce531898be3b01f92/docs/recipes/pre-releases.md)) and I can replicate the problem. I've combined both recipes...

I forgot to mention it here, but I created [a PR](https://github.com/semantic-release/semantic-release/pull/1971) with the possible fix for the workflow that I mentioned before. Just letting you know in case Github hasn't...