@googleapis/api-bigquery Please close if this isn't a good time for a release.

I am cutting this because the Yoshi team is releasing clients with the new endpoints (bigquery.googleapis.com instead of www.googleapis.com).

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@plamut Is it OK to release BigQuery?

@busunkim96 I don't know the roadmap, but it's probably fine. However, if not urgent, it would IMO make sense to wait a bit more for the currently open BigQuery PRs to get reviewed and merged (at least for those that don't require significant extra work).

@plamut Thank you! Justin's asked that this endpoint change land in the first half of the week, so I will proceed with the release.

Release is at https://github.com/googleapis/google-cloud-python/releases/tag/bigquery-1.20.0

The release build has started, the log can be viewed here. 🌻

🥚 You hatched a release! The release build finished successfully! 💜