rev the bigquery minimum versions to a big number (#2233) #2249
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
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.
resolves #2233
Description
I raised the lower bound on most of the bigquery dependencies to whatever the current version I have installed is - I'm sure this will break someone's workflow, but hopefully this will avoid us having to deal with it too often, and hopefully prevent us from getting surprised by requirements updates that add a feature we were inadvertently relying on.
While I was in here I also bumped the version and fixed a bug in the unit tests where they would fail if the version number was a final release version (but not if they were an alpha/beta/rc)
Checklist
This PR includes tests, ortests are not required/relevant for this PRCHANGELOG.mdand added information about my change to the "dbt next" section.