Prepare for 2.0 release #3
Merged
Conversation
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
|
👍 LGTM Should we update the Travis scripts to pull in the new release? |
Member
Author
|
I'm not sure - we could do that, but then we'd have to update them all again once we make the proper release. It's a shame the "latest" URL I'm using doesn't include pre-releases - there doesn't seem to be a general URL for the "actual latest" release. We could just release 0.10 and be done with it though? I've worked on a bunch of libraries locally I don't have PRs for yet and it all seems to be working out so far. Can always make a .1 if it turns out to be buggy. |
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.
No description provided.