Update travis to always use the latest release#6
Merged
Conversation
Member
|
I think in the absence of a real dependency manager like npm or bower I'd rather if we had to specifically state the version we're using. The latest release doesn't always work with every library, and I'd rather if we only used versions we know can compile this library. We can make this easier by putting I'll pull your changes and make the modifications for this. Thanks! |
Merged
Member
Author
|
Ah sure, that makes sense. I'd been making this change in the core libraries (which I feel probably should be tested against the latest version) and just noticed builds were enabled for |
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
2 participants
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'm not sure where exactly this should be applied, so if merging here is no good just close it and take the updated
.travis.yml.