chore: Default ReadTheDocs to Ubuntu / Python latest
#750
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I noticed this because `3.7` is EOL'd by upstream, plus `24.04` will be released later this month (although may take RTD a bit longer to pull it in). Looking at [the docs](https://docs.readthedocs.io/en/stable/config-file/v2.html), there's a `latest` variant for both. It comes with a warning that using latest may unexpectedly break builds if the project isn't compatible... But I think for our use case the odds that it will break are extremely low (and in fact we'd want to know it's broken so we could fix it!) Plus if it starts breaking, it's not hard to temp pin it to an older version. So all-in-all, both lower maintenance and faster realization of breakage if we default to latest on both of these.
jeffwidman
force-pushed
the
default-rtd-to-ubuntu-python-latest
branch
from
277a232 to
6fd22da
Compare
|
Hmm... something weird with GitHub's diff generation when I force-pushed from a Codespace... re-opened at: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed this because
3.7is EOL'd by upstream, plus24.04will be released later this month (although may take RTD a bit longer to pull it in).Looking at the docs, there's a
latestvariant for both.It comes with a warning that using latest may unexpectedly break builds if the project isn't compatible... But I think for our use case the odds that it will break are extremely low (and in fact we'd want to know it's broken so we could fix it!) Plus if it starts breaking, it's not hard to temp pin it to an older version.
So all-in-all, both lower maintenance and faster realization of breakage if we default to latest on both of these.