Releasing from the first changelog entry

[Fryuni]

Description:

Inconsistent generation of releases for the first changelog entry

Tag:

0.0.1-beta1

Workflow:

- name: Release
  uses: docker://antonyurchenko/git-release:v3
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    DRAFT_RELEASE: "true"
    PRE_RELEASE: "false"
    CHANGELOG_FILE: "CHANGELOG.md"
    ALLOW_EMPTY_CHANGELOG: "true"
    ALLOW_TAG_PREFIX: "false"

Changelog:

# Changelog

## [0.0.1-beta1](https://github.com/croct-tech/plug-js/tree/0.0.1-beta1) (2020-03-22)

[Full Changelog](https://github.com/croct-tech/plug-js/compare/20cdc015ba4f2f5b2ec9881e9bd72ea09b6bc381...0.0.1-beta1)

Log:

WARNING 'ALLOW_EMPTY_CHANGELOG' enabled              
FATAL empty changelog for requested version: '0.0.1-beta1' 

Problem:

This regex will match the line starting with [Full Changelog] and return one line above.

Is there a reason for this check before returning len(content)? This matching will cause all releases from a first entry that have any line starting with a link to have an incomplete body, and is not consistent with what would happen with multiple entries.
With multiple entries like:

# Changelog

## [0.0.1-beta2](https://github.com/croct-tech/plug-js/tree/0.0.1-beta2) (2020-03-22)

[Full Changelog](https://github.com/croct-tech/plug-js/compare/0.0.1-beta1...0.0.1-beta2)

## [0.0.1-beta1](https://github.com/croct-tech/plug-js/tree/0.0.1-beta1) (2020-03-22)

Some message
[Full Changelog](https://github.com/croct-tech/plug-js/compare/20cdc015ba4f2f5b2ec9881e9bd72ea09b6bc381...0.0.1-beta1)

generating a release for the tag 0.0.1-beta2 will include the full changelog link on the release body, but would not on 0.0.1-beta1

[anton-yurchenko]

Hello @Fryuni,
Your changelog does not seem to follow keepachangelog guidelines.
I believe that your issue will be fixed as soon as you change your changelog format.

[Fryuni]

Keepachangelog does not specify that there should not be comments on a release, and a link at the start of plain line will still break the first release even with the link url at the bottom like they do.

This changelog is exactly the one generated by the github changelog generator, which is also based on keepachangelog, the difference being linking to the tree at the title with the diff below and the inline links instead of at the end, it gives the same result.

We ended up using a different approach, so no worries. Just know that it will break it there is any comment starting with a link

[anton-yurchenko]

You are right @Fryuni, links in a body of the release should be ignored.
Thank you.