-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Point /latest to latest released version (including pre-releases) #4326
Comments
rtd doesn't support automatically pointing latest to the new pre-release version. But you can set the commit/branch (I think it works with tags too) to which latest point in the admin panel of your project. |
@stsewd True, but that requires manual intervention for every release. Ideally, |
If I understand correctly, this is a big change regarding the concept around I think you are proposing to use
At this moment, no. |
@humitos Thanks for the clarification. Perhaps there should be a separate alias, then, that points to the latest release and does not exclude pre-releases? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still valid, but requires a design decision |
I'd prefer we address this with the version rules feature I've been looking for -- #4001 |
I would love a convenient tag other than |
Currently
stable
is an alias for the latest stable git tag andlatest
points to the HEAD of a specified git branch. As was pointed out in #965, users usually only deal with released versions (rather than development versions). I would likelatest
to be an alias for the latest pre-release version. Is this possible?The text was updated successfully, but these errors were encountered: