docs/Changelog: 9.0 release notes are missing

[cfra]

The changelog for tenacity latest at https://tenacity.readthedocs.io/en/latest/changelog.html shows only release notes up to 8.2.2 while the released version on PyPI and on GitHub is 9.0.0.

This seems wrong to me.

[margaretfero-codepath]

The release is up to 9.1.4 and the changelog still only has release notes to 8.2.2. Is the changelog deprecated, or is it just that no one's gotten around to fixing this yet?

[G-ChandraSekhar]

Looked into why this is stuck. Both latest and stable are showing failed builds on the public dashboard (app.readthedocs.org/projects/tenacity/builds/) — confirmed failures, not just old builds. That's why the changelog is frozen at 8.2.2 even though 8.2.3 through 9.1.4 have shipped since: nothing has published successfully.

Root cause, from the actual build logs: RTD's checkout runs git clone --depth 1 followed by git fetch --depth 50. reno (used for the changelog via doc/source/changelog.rst) walks the commit graph to resolve version boundaries, and 50 commits of history isn't enough on this repo anymore. Every build fails the same way, e.g.:

Build #21667866:
File ".../reno/scanner.py", line 749, in _topo_traversal
entry = all[sha]
KeyError: b'42483eb3187d309ebae0db87a1b05b6078ea95f4'

Build #21667870:
File ".../reno/scanner.py", line 641, in _get_current_version
commit = self._repo[commit.parents[0]]
KeyError: b'3e2244535ccfbb6a4b7fdd77bfc9aa61a1302302'

Same root cause, two different entry points inside reno's history walk.

I reproduced this locally: ran RTD's exact checkout sequence (depth-1 clone, then depth-50 fetch) against a fresh clone, confirmed reno report fails with the same KeyError. Ran git fetch --unshallow --tags afterward, and reno report then succeeds, correctly resolving the full version history back to 1.0.0.

Fix is a small addition to .readthedocs.yml — a post_checkout job that unshallow the clone before the Sphinx build runs. I'll open a PR for it shortly.