Gren release and changelog lag one tag behind

[martingerdin]

Thank you for gren!

Now, if I do:

echo "This is a test" >> README.md
git add README.md
git commit -m "Add README"
git push
git tag v1
git push --tags
hub issue create -m "Update README"
echo "Update" >> README.md
git add README.md
git commit -m "Fix #1"
git push
git tag v2
git push --tags
gren release # I expect to see "Update README" in these release notes
echo "Update again" >> README.md
git add README.md
git commit -m "Update again"
git push
git tag v3
git push --tags
gren release # But instead I see "Update README" here

Then I would expect to see "Update README" in the release notes for v2, because "#1" was closed before the commit was tagged v2. It doesn't, however, instead it shows up in the v3 release.

Is this the expected behavior, and am I misunderstanding something? If so, what can I do to have "Update README" show up in the v2 release notes?

[rchabin]

Same issue for me 👍

[erickertz]

Thanks for Gren! Also experiencing this issue.

[alexcanessa]

What version of gren are you using? Try the new version and see if still an issue please 🙏

[erickertz]

version 0.17.0. this is the first time I've used gren. It always seems to skip the first commit in a release in the notes for some reason, which I think is what the OP is also saying. For instance:

1. Create notes for 1.0.0:
   gren release --override --data-source=commits --tags 1.0.0

2. Create notes for 1.0.1:
   gren release --override --data-source=commits --tags 1.0.1

OUTCOME: 1.0.1 will be missing the notes from the first commit.

Also, doing:
gren release --override --data-source=commits --tags 1.0.1..1.0.0

OUTCOME: 1.0.1 will be missing the notes from the first commit.

[alexcanessa]

Ok I'll have a look, ta

[idlem1nd]

Also seeing this in version 0.17.0.

[Tybot204]

Also seeing this issue, but with prs given as the data source. If a merged PR commit is tagged, it will be missing from that tag's release notes.

Seems related to #128?

[mlrv]

Any update on this?

[JuergenSimon]

Actually it's a little worse than simply lagging for me. The commits that coincide with the tag simply do not enter the changelog.

[alexcanessa]

This should be closed by #220

And duplicate of #219