| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@jonparrott I realized I needed patch updates for BigQuery and Language, so there is a teeny commit since you approved. So sorry. |
Sorry, something went wrong.
|
@bjwatson I'd really like to get #2844 in, which requires you giving the 👍 to 1.0.2rc0 so there can be a real-live 1.0.2 /cc @nathanielmanistaatgoogle Though we may just cut these releases today and say shucks. |
Sorry, something went wrong.
BigQuerygit log bigquery-0.22.0..ya-release -- bigquery/
Bigtablegit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- bigtable/
Core$ git log core-0.22.0..ya-release -- core/ Only change is #2828 (and version bump) Datastoregit log 0.21.0..ya-release -- datastore/
DNSgit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- dns/
Error Reportinggit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- error_reporting/
Natural Language$ git log language-0.22.0..ya-release -- language/ reveals #2841 is only change in source. The only reason to bump is the core bump, which has #2828 Logginggit log 0.21.0..ya-release -- logging/
Monitoringgit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- monitoring/
Pub / Subgit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- pubsub/
Resource Managergit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- resource_manager/
Runtime Configgit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- runtimeconfig/
Speechgit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- speech/
Storagegit log 0.21.0..ya-release -- storage/
Translategit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- translate/
Visiongit log --abbrev-commit --pretty=format:"%h %s" 0.21.0..HEAD -- vision/
|
Sorry, something went wrong.
|
@dhermes I filled in the notes. LMK if there's anything else I can do to help with this! |
Sorry, something went wrong.
|
@daspecster 0.21.1..HEAD is (probably) the wrong range for most of these. google-cloud was the only thing released at 0.21.1, everything else at 0.21.0 (except for the ones that have already started their own tag family: core-*, bigquery-* and language-*) |
Sorry, something went wrong.
|
@dhermes good call. I updated the notes. There were a few PRs missing from between the 0.21.1. |
Sorry, something went wrong.
|
@dhermes Sorry for the delay. I was in bad shape yesterday. Doing much better today after lots of sleep. The grpcio 1.0.2 release looks great, and I'm going to publish (gapic|grpc)-google-cloud-logging-v2 0.9.0 with a Beta development status. |
Sorry, something went wrong.
| 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', |
| REQUIREMENTS = [ | ||
| 'google-cloud-core >= 0.21.0, < 0.22dev', | ||
| 'google-cloud-core >= 0.22.1, < 0.23dev', | ||
| 'grpcio >= 1.0.0, < 2.0dev', |
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 grpcio >= 1.0.2 deps and switching to version 0.90 (time travel from 0.14) of logging. I'm ready to push the big red button? |
Sorry, something went wrong.
|
system-tests failure due to: Collecting google-cloud-happybase<0.23dev,>=0.22.0 (from google-cloud==0.22.0) Could not find a version that satisfies the requirement google-cloud-happybase<0.23dev,>=0.22.0 (from google-cloud==0.22.0) (from versions: 0.20.0, 0.21.0) No matching distribution found for google-cloud-happybase<0.23dev,>=0.22.0 (from google-cloud==0.22.0) |
Sorry, something went wrong.
|
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 happybase to PyPI first). |
Sorry, something went wrong.
Sorry, something went wrong.
|
It is likely a mistake that google-cloud pulls in google-cloud-happybase. |
Sorry, something went wrong.
|
@tseaver You think so? I did it on purpose when the umbrella came into existence, but maybe shouldn't have? |
Sorry, something went wrong.
|
I think we should treat google-cloud-happybase as a "downstream" project, which a) breaks the cyclic dependency, and b) prevents resurrecting any licensing issue. |
Sorry, something went wrong.
|
SGTM, @jonparrott WDYT? Also, I just did the following: git tag 0.22.0 git tag bigquery-0.22.1 git tag bigtable-0.22.0 git tag core-0.22.1 git tag datastore-0.22.0 git tag dns-0.22.0 git tag error-reporting-0.22.0 git tag language-0.22.1 git tag logging-0.22.0 git tag monitoring-0.22.0 git tag pubsub-0.22.0 git tag resource-manager-0.22.0 git tag runtimeconfig-0.22.0 git tag speech-0.22.0 git tag storage-0.22.0 git tag translate-0.22.0 git tag vision-0.22.0 followed by git push official 0.22.0 git push official bigquery-0.22.1 git push official bigtable-0.22.0 git push official core-0.22.1 git push official datastore-0.22.0 git push official dns-0.22.0 git push official error-reporting-0.22.0 git push official language-0.22.1 git push official logging-0.22.0 git push official monitoring-0.22.0 git push official pubsub-0.22.0 git push official resource-manager-0.22.0 git push official runtimeconfig-0.22.0 git push official speech-0.22.0 git push official storage-0.22.0 git push official translate-0.22.0 git push official vision-0.22.0 Now we'll see if the CircleCI deploy to PyPI works |
Sorry, something went wrong.
|
Here are the tag builds:
|
Sorry, something went wrong.
Sorry, something went wrong.
|
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: (([a-z]+)-)?([0-9]+)\.([0-9]+)\.([0-9]+) Similarly, the Python regex doesn't pick it up: $ CIRCLE_TAG=error-reporting-0.22.0 python scripts/circleci_tagged_pkg.py Invalid tag name: error-reporting-0.22.0. Expected ^((?P<pkg>[a-z]+)-)?([0-9]+)\.([0-9]+)\.([0-9]+)$ |
Sorry, something went wrong.
|
@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 |
Sorry, something went wrong.
|
OK, for now, I manually finished pushing: $ cd error_reporting $ python setup.py sdist bdist_wheel $ twine upload dist/* $ $ cd ../resource_manager $ python setup.py sdist bdist_wheel $ twine upload dist/* $ $ cd .. $ git clone git@gist.github.com:a4e097f2f80fd490b256fc3aa2b4a46b.git $ cd a4e097f2f80fd490b256fc3aa2b4a46b/ $ python setup.py sdist bdist_wheel $ twine upload dist/* |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
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.
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.
| Back | FazBrowse Home | New Git URL |
We want to update
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.
See also: googleapis/google-cloud-python-happybase#19