Changelog entries missing for > 6.3.0

[hynek]

There seems to be a bit of inconsistency between:

• https://pypi.org/project/tenacity/#history (latest release 7.0.0)
• https://tenacity.readthedocs.io/en/latest/changelog.html (6.3.0)
• https://github.com/jd/tenacity/releases (5.1.4)

Any chance we could learn what the supposedly breaking changes were? 😇

[jd]

The idea was to use reno to manage release notes, except that this has been missed multiple times.

I've added a check for this now in #285 so we're sure it stops happening.

If anyone is brave enough to write previous changelog entries, we can try to put them somewhere I guess.

[pheanex]

This is the list of commits since 6.3.1:

• Avoid including tests when packaging (#281)
• Warn when calling retry() on retry_base (#269) (#270)
• Copy whole internal state when retry_with (#233) (#278)
• CI: Enable black (#277)
• Merge pull request #275 from jd/py39
• Merge branch 'master' into py39
• Refactor: Remove old compat support code (#274)
• Chore: Add support for Python 3.9
• Pull Request for fix-ci (#276)
• Fix: Remove saythanks (dead)

@jd can you tell which one required a major version bump, so users know what to watch out for?

[jd]

#274 removed compat code that's the culprit for the bump

[max-sixty]

FYI GH releases is behind:

[jd]

I don't use GitHub releases, I just tag and push. The fact that this has been used once now shows this forever, it's sad.

It'd be great to have more automation around this, so if anybody has a hint on how to improve the situation, happy to implement stuff.

[max-sixty]

If it's a single one, you can delete it @jd https://docs.github.com/en/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release

[jd]

Just did, thank you!

[nzig]

Hi @jd, it looks like this happened again for 8.1.0. There are no release notes at https://tenacity.readthedocs.io/en/latest/changelog.html.

Would you mind rebuilding the changelog 🙏 ?