build: fix release build

[busunkim96]

Switch to release publish bot for reporting status back to GitHub release PRs.

[plamut]

Now this will be handy, thanks!

P.S.: I'm not really familiar with Kokoro config and don't have insight into internal logs, thus I cannot really say in advance whether it will fix the release build, sorry, :)

[plamut]

Seems like the build failed, but I cannot see the logs, since not all checks have finished yet.

Edit: Aha, making a script runnable is a good idea. 😆

[busunkim96]

Confirmed by running the release build on my branch that this combination of files is sufficient https://source.cloud.google.com/results/invocations/c20fabd9-c754-49b7-9bec-dc91f3f1b3ba/targets/cloud-devrel%2Fclient-libraries%2Fpython%2Fgoogleapis%2Fpython-bigquery-storage%2Frelease%2Frelease/log (release itself failed because version 1.0.0 already exists)

[plamut]

Uploading the wheel 1.0.0 failed, is there something hardcoded such as the name or the version?

Uploading distributions to https://upload.pypi.org/legacy/
Uploading google_cloud_bigquery_storage-1.0.0-py2.py3-none-any.whl
...
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
File already exists. See https://pypi.org/help/#file-name-reuse for more information.

[plamut]

@busunkim96 Does this mean we can (force) merge this and then create a new release PR?