Bump google dependency upper bounds, remove six
#57
Conversation
This file contains 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
jtcohen6
force-pushed
the
dependame/google-deps
branch
from
e9e34c8 to
2979ffb
Compare
kwigley
approved these changes
Nov 8, 2021
siephen
pushed a commit
to AgencyPMG/dbt-bigquery
that referenced
this pull request
May 16, 2022
* Bump google deps, rm six * Update changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not sure why
dependabotisn't working forsetup.pyhere either. In any case:six, which we added way back when to fix a dependency mistake indbt-bigquery==1.23.0; we now require>=1.25.0(put an upper bound on bigquery dbt-core#2007, Bigquery: import error with v.1.23.0 googleapis/google-cloud-python#9965). We haven't supported python2 for some time, so I don't see any reason to keepsixhanging around