Description
If using semantic-release branch config such as { name: 'AWR-+([0-9])', prerelease: true } where AWR is the ticket prefix, semantic-release will release pre-release versions of these as something like 3.0.0-AWR-1234.3
Since this version includes the ticket number, semantic-release-jira-notes converts this to a link. The problem with this is that semantic-release also creates a link for that version number, such as
[3.0.0-AWR-1234.3](https://gitlab.com/our_repo/compare/v3.0.0-AWR-1234.2...v3.0.0-AWR-1234.3)
Renders as markdown:
3.0.0-AWR-1234.3
So after this plugin converts AWR-1234 to a link, this changes the above to
[3.0.0-[AWR-1234](https://our_subdomain.atlassian.net/browse/AWR-1234).3](https://gitlab.com/our_repo/compare/v3.0.0-[AWR-1234](https://our_subdomain.atlassian.net/browse/AWR-1234).2...v3.0.0-[AWR-1234](https://our_subdomain.atlassian.net/browse/AWR-1234).3)
Renders as markdown:
[3.0.0-AWR-1234.3](https://gitlab.com/our_repo/compare/v3.0.0-[AWR-1234](https://our_subdomain.atlassian.net/browse/AWR-1234).2...v3.0.0-[AWR-1234](https://our_subdomain.atlassian.net/browse/AWR-1234).3)
Which obviously completely breaks the markdown.
Perhaps the first line of the release notes should be excluded from the regex to avoid this?