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.

Sign up for GitHub

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

Jump to bottom

Have a "latest" release and refer to it in the docs #366

Open
ageorgou opened this issue Apr 9, 2019 · 2 comments
Open

Have a "latest" release and refer to it in the docs #366

ageorgou opened this issue Apr 9, 2019 · 2 comments

Comments

@ageorgou
Copy link
Contributor

ageorgou commented Apr 9, 2019 •
edited
Loading

Having a "latest" release, to be updated whenever a new release is created, will make it easier to always find the latest version from a static link, and save us the effort of updating the README every time.
@ageorgou
Copy link
Contributor Author

ageorgou commented Jun 10, 2019 •
edited
Loading

This should be simple. From GitHub's docs:

If you'd like to link directly to a download of your latest release asset you can link to /owner/name/releases/latest/download/asset-name.zip.

And the URL /releases/latest also points to the latest release.

@giordano
Copy link
Contributor

giordano commented Jun 11, 2019 •
edited
Loading

We can point to the latest release, but currently the docs link diretly to the JAR, not the release page, and the JAR name will change with version. We'd have to point to the release page or rename the JAR to be version-independent? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@giordano @ageorgou