What happened:

We recently made several release notes via chronicle whose release notes later needed to be handed edited.

• https://github.com/anchore/vunnel/releases/tag/v0.15.1 is missing fix: respect "not applicable" tag in Mariner Linux provider vunnel#244
• https://github.com/anchore/grype/releases/tag/v0.64.2 erroneously included grype v0.64.0 template zeroes the template content grype#1388, and I had to add changelog-ignore, run the release, and then remove it
• https://github.com/anchore/grype/releases/tag/v0.64.1 erroneously omitted grype v0.64.0 template zeroes the template content grype#1388, and it had to be added by hand to the release notes

What you expected to happen:

Two expectations were not met here:

1. The changelog was initially generated with some error (see above)
2. In 2 of these cases, the changelog looked correct locally, but then re-introduced the error when run in CI.

How to reproduce it (as minimally and precisely as possible):

I'm not sure; chronicle doesn't support regenerating release notes for an existing release

Anything else we need to know?:

The vunnel release closed an issue in a different repo, which seems to have confused chronicle, likely because the GH token I was using had minimal permissions, and probably couldn't read issues on the other repo.

The two grype releases were in pretty rapid succession.

Environment:

• Output of chronicle version: