-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update versions for mega-release. #2846
Conversation
@jonparrott I realized I needed patch updates for BigQuery and Language, so there is a teeny commit since you approved. So sorry. |
@bjwatson I'd really like to get #2844 in, which requires you giving the 👍 to Though we may just cut these releases today and say shucks. |
BigQuery
Bigtable
Core
Only change is #2828 (and version bump) Datastore
DNS
Error Reporting
Natural Language
reveals #2841 is only change in source. The only reason to bump is the Logging
Monitoring
Pub / Sub
Resource Manager
Runtime Config
Speech
Storage
Translate
Vision
|
@dhermes I filled in the notes. LMK if there's anything else I can do to help with this! |
@daspecster |
@dhermes good call. I updated the notes. There were a few PRs missing from between the |
@dhermes Sorry for the delay. I was in bad shape yesterday. Doing much better today after lots of sleep. The |
@@ -50,13 +50,13 @@ | |||
|
|||
|
|||
REQUIREMENTS = [ | |||
'google-cloud-core >= 0.21.0, < 0.22dev', | |||
'google-cloud-core >= 0.22.1, < 0.23dev', | |||
'gapic-google-cloud-logging-v2 >= 0.14.0, < 0.15dev', |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@@ -50,13 +50,13 @@ | |||
|
|||
|
|||
REQUIREMENTS = [ | |||
'google-cloud-core >= 0.21.0, < 0.22dev', | |||
'google-cloud-core >= 0.22.1, < 0.23dev', | |||
'grpcio >= 1.0.0, < 2.0dev', |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
We want to update - `google-cloud-bigquery` - `google-cloud-datastore` - `google-cloud-logging` - `google-cloud-storage` - `google-cloud-core` And then update `google-cloud` to re-wrap the latest versions of each. However, to avoid having packages in `google-cloud` with conflicting versions of `google-cloud-core`, we must release all packages.
Also upgrading logging from 0.14.x to 0.90.x
OK I just added the I'm ready to push the big red button? |
|
Yup, same thing happened in googleapis/google-cloud-python-happybase#19, totally expected. Not sure how to resolve in general (I guess I could've pushed a b0rken |
It is likely a mistake that |
@tseaver You think so? I did it on purpose when the umbrella came into existence, but maybe shouldn't have? |
I think we should treat |
SGTM, @jonparrott WDYT? Also, I just did the following:
followed by
Now we'll see if the CircleCI deploy to PyPI works |
Here are the tag builds:
|
OK sent #2852. As for the two builds that didn't trigger, it is indeed I who have the stupid. My regex isn't build to pick them up:
Similarly, the Python regex doesn't pick it up:
|
@jonparrott It's worth noting that all of those tag builds were throttled, with the worst waiting an hour to run: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/540#usage-queue/containers/0 On the plus side, it's great that CircleCI tells us how long they were throttled and tells us what builds caused them to get stuck in a queue |
OK, for now, I manually finished pushing:
|
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
Update versions for mega-release.
We want to update
google-cloud-bigquery
google-cloud-datastore
google-cloud-logging
google-cloud-storage
google-cloud-core
And then update
google-cloud
to re-wrap the latest versions of each.However, to avoid having packages in
google-cloud
with conflicting versions ofgoogle-cloud-core
, we must release all packages.See also: googleapis/google-cloud-python-happybase#19