Skip to content
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

Closed
sloria opened this issue Jul 3, 2018 · 8 comments
Closed

Point /latest to latest released version (including pre-releases) #4326

sloria opened this issue Jul 3, 2018 · 8 comments

Comments

@sloria
Copy link

sloria commented Jul 3, 2018

Currently stable is an alias for the latest stable git tag and latest 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 like latest to be an alias for the latest pre-release version. Is this possible?

@sloria sloria changed the title Point latest to latest released version (including pre-releases) Point /latest to latest released version (including pre-releases) Jul 3, 2018
@stsewd
Copy link
Member

stsewd commented Jul 3, 2018

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.

@sloria
Copy link
Author

sloria commented Jul 3, 2018

@stsewd True, but that requires manual intervention for every release. Ideally, latest (or some other alias) would automatically point the latest release.

@humitos humitos added the Support Support question label Jul 3, 2018
@humitos
Copy link
Member

humitos commented Jul 3, 2018

If I understand correctly, this is a big change regarding the concept around latest. We use latest as the "most recent change/commit" in the repository tied to a specific branch (master by default in Git -but this can be changed from the admin).

I think you are proposing to use latest for "latest pre-release" and stable for "latest release" which will break the concept behind the latest alias.

Is this possible?

At this moment, no.

@sloria
Copy link
Author

sloria commented Jul 3, 2018

@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?

@stale
Copy link

stale bot commented Jan 10, 2019

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 10, 2019
@stsewd stsewd added Feature New feature Needed: design decision A core team decision is required and removed Status: stale Issue will be considered inactive soon Support Support question labels Jan 10, 2019
@stsewd
Copy link
Member

stsewd commented Jan 10, 2019

This is still valid, but requires a design decision

@agjohnson
Copy link
Contributor

I'd prefer we address this with the version rules feature I've been looking for -- #4001

@agjohnson agjohnson removed Feature New feature Needed: design decision A core team decision is required labels Jan 10, 2019
@EwoutH
Copy link
Contributor

EwoutH commented Sep 24, 2024

I would love a convenient tag other than stable and latest that always points to the latest pre-release. A native prerelease tag would be very convenient!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants