automatically create latest/ symlink in docs for tagged builds#222
Merged
germanattanasio merged 1 commit intomasterfrom Mar 29, 2016
Merged
automatically create latest/ symlink in docs for tagged builds#222germanattanasio merged 1 commit intomasterfrom
germanattanasio merged 1 commit intomasterfrom
Conversation
Current coverage is
|
Contributor
Author
|
@germanattanasio can you do a version bump to validate this? Also, I see a |
This file contains hidden or 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
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.
Summary
This is to answer the docs team's request to be able to link to the latest release's javadoc without continually having to update things. It should also make life easier on us.
Other Information
This actually points to the latest tag, so if you, say, release v3.0.0 and then go back and publish v2.9.1 with a bugfix, the latest/ link will change to v2.9.1 until you release a new v3.x. (Or you change it manually in the
gh-pagesbranch.)I'm sending this as a PR rather than committing it so that @germanattanasio can review it and choose when to test it on a new release.