Version dependencies / Release 0.4.3 #40
Merged
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.
While building the v0.4.2 gem release there were several warnings regarding open ended dependencies. For example:
My first attempt to fix this issue was e588d96 which was released as 0.4.2. Unfortunately, the bundler versioning broke the [build](https://travis-ci.org/opentracing/opentracing-ruby/builds/444695333. While there isn't technically anything wrong with the ruby code, the officially released gem should have a passing build.
I think it's probably overkill to yank 0.4.2, but I'd like to release this as 0.4.3. Do these changes look ok and does the release plan sound reasonable to everyone?
cc: @indrekj @itsderek23