Update google cloud dependencies

[max-sixty]

resolves #3155

Description

As per the last one of these, another bump to latest.

These are now more stable, so you may want to only pin the major version — let me know if you'd like me to make that change.

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

[jtcohen6]

Thanks @max-sixty!

These are now more stable, so you may want to only pin the major version — let me know if you'd like me to make that change.

I'd love to be in a place of having major-version boundaries for these. It's not such a chore to upgrade them every minor release, but tighter pins result in inevitable delays. Could you say a bit more about the improved stability, based on what you've observed / read / heard?

[max-sixty]

I'd love to be in a place of having major-version boundaries for these. It's not such a chore to upgrade them every minor release, but tighter pins result in inevitable delays. Could you say a bit more about the improved stability, based on what you've observed / read / heard?

I don't have a more reliable signal than my own experience, unfortunately. I'm trying to think of a good one — maybe whether dbt has had to make any changes to its library when upgrading — do you know whether it has?

In my experience — this used to be a big problem and I used to complain about it — and in the last year at least, I haven't found it a problem at all.

[max-sixty]

Any thoughts on merging? I see 0.19.1 came out today.

[jtcohen6]

maybe whether dbt has had to make any changes to its library when upgrading — do you know whether it has?

I don't believe we've had to do this for some time. At the same time, I know we see some deprecation warnings from the BigQuery python client, e.g.

Client.dataset is deprecated and will be removed in a future version. Use a string like 'my_project.my_dataset' or a cloud.google.bigquery.DatasetReference object, instead.

In any case, I think I'd be open to trying to relax the pins (major-version upper bounds instead of minor ones) in v0.20. We could merge that change now, and see if we run into any trouble between now and the final v0.20.0 release.

[max-sixty]

Great! Done!

[jtcohen6]

Nice, thank you! Could you also remove the associated comment ("these are more tightly pinned"), and add a changelog entry?

[max-sixty]

Nice, thank you! Could you also remove the associated comment ("these are more tightly pinned"), and add a changelog entry?

Good spot, both done

[jtcohen6]

Thanks @max-sixty!