Remove release notes in docs #152
Conversation
|
Also, the latest build on RTD is from 3 years ago :) https://readthedocs.org/projects/freetype-py/builds/ |
|
Yes, I need to upload the new doc. Best would be to have a github action to do that automatically. Any experience on that? |
|
Normally RTD will just rerender automatically on new commits to main, but I guess the webhook is broken. |
|
If you're logged into readthedocs.org, go to the project, and then the admin panel. Then it's under "integrations" |
|
I configured everything on readthedocs but the doc still seems outdated. |
|
It looks like the current ci runs twine manually, but even twine itself doesn't do that any more: |
|
I believe this is relevant: pypa/twine#999 . FWIW, skip-python moved to trusted publisher pypi workflow in January, because the |
|
Last pass on Aug. 21, 2023 That's just updating between Two examples. Looks like it is a server change there. Except the first failure, every failure after were about |
|
We definitely don't have a |
|
Okay, kind of unrelated, but the docs stopped updating between Dec 17, 2018 and May 15, 2022. Then it broke in aug 2024 between 23rd and 21st. Anyway, it works now. While I think something needs to be done about the massively outdated release notes, I rather think importing them from the release page to the doc directory is better than deleting them - to keep the docs in one place. |
|
Keeping the release notes inside the repo is also perhaps more appropriate in light of the possibility that the repo may move - and github based release notes will be lost in such cases (#188). |
Since the release notes are now on the GH release pages.