deps: add a few missing artifacts to the deps bom #143
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
* expand google-cloud-core to a bom, so that we fix google-cloud-core-http's version in the hbase adapter * google-http-client-bom, it's a transitive dep for google-cloud-bigtable and a direct dep of the hbase adaptor * opencensus-* add a bunch more relevant opencensus deps. There is no opencensus-bom, so we enumerate any that might be useful
Codecov Report
@@ Coverage Diff @@
## master #143 +/- ##
=========================================
Coverage ? 81.74%
Complexity ? 952
=========================================
Files ? 97
Lines ? 5927
Branches ? 327
=========================================
Hits ? 4845
Misses ? 904
Partials ? 178Continue to review full report at Codecov.
|
kolea2
approved these changes
Jan 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for context and/or discussion)