Skip to content

Update travis to always use the latest release #6

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

Merged
merged 1 commit into from
Nov 22, 2014
Merged

Conversation

garyb
Copy link
Member

@garyb garyb commented Nov 22, 2014

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.

@joneshf
Copy link
Member

joneshf commented Nov 22, 2014

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 $TAG under env and just updating that when we want to update the version.

I'll pull your changes and make the modifications for this. Thanks!

@joneshf joneshf mentioned this pull request Nov 22, 2014
@garyb
Copy link
Member Author

garyb commented Nov 22, 2014

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 argonaut in travis too so thought I'd pass it on.

@joneshf joneshf merged commit 0a75610 into master Nov 22, 2014
@garyb garyb deleted the better-travis branch November 22, 2014 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants