[BUG] No changelog data for 3.2.2

[christian-hawk]

Version 3.2.2 was released but there is no information about it in changelog

passport-saml/CHANGELOG.md

Line 95 in 84ef919

## v3.2.1 (2022-01-21)

[srd90]

While waiting changelog update here is reference to 3.2.2's content: https://github.com/node-saml/passport-saml/releases/tag/v3.2.2

See security advisory GHSA-m974-647v-whv7

[christian-hawk]

Now that 3.2.3 is released, there is changelog content for 3.2.2 but 3.2.3 is missing:

https://github.com/node-saml/passport-saml/blob/v3.2.3/CHANGELOG.md#v322-2022-10-11

Changes are shown in the upper 3.x section, even that 3.2.3 is released and published.

As the process of releasing is done manually by release-it by @cjbarth , I cannot find any problem for now. The changelog is created with the current branch name instead of the new tag. Maybe is related to the post hook npm run changelog in .release-it.json file.

[cjbarth]

The changelog is built automatically from PRs and their labels by pulling data from GitHub. At the time I go to make another release, there is no tag for the latest release on GitHub yet (or anywhere). So, the tool can only specify the commits remaining on the branch after the last tag. I'm trying to get in the habit of modifying the generated changelog to specify the version I'm about to release, but, if I forget, the release contains what is at the top of the changelog. Does that make sense?

[christian-hawk]

@cjbarth the way I see the release X.Y.z should be in X.Y.z section. Please also keep in mind that ci tools such as dependabot and others, links to a non-existant changelog section.

[cjbarth]

the release X.Y.z should be in X.Y.z section

I'm not sure I follow. Isn't that the way most of the CHANGELOG is?

ci tools such as dependabot and others, links to a non-existant changelog section

Do you happen to have a reference for how such tools parse a CHANGELOG file so we can make sure ours matches the parsable format?