Skip to content

chore: release 1.31.2 #256

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

Merged
merged 1 commit into from
Aug 16, 2021
Merged

chore: release 1.31.2 #256

merged 1 commit into from
Aug 16, 2021

Conversation

busunkim96
Copy link
Contributor

@busunkim96 busunkim96 commented Aug 16, 2021

Manually updating version and Changelog for record keeping purposes.

@busunkim96 busunkim96 requested a review from a team as a code owner August 16, 2021 20:47
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Aug 16, 2021
@busunkim96 busunkim96 changed the base branch from master to v1 August 16, 2021 20:47
@tseaver
Copy link
Contributor

tseaver commented Aug 16, 2021

I can't see logs from the failed OwlBot Post Processor job. :(

@busunkim96
Copy link
Contributor Author

google-api-core==1.31.2 with the field mask fix is now released @BenRKarl

@busunkim96
Copy link
Contributor Author

Hmm I initially had master as the base branch and then switched it to v1. Maybe that confused the post processor?

@tseaver
Copy link
Contributor

tseaver commented Aug 16, 2021

I see the release on the cheeseshop: https://pypi.org/project/google-api-core/1.31.2/

@busunkim96 busunkim96 merged commit affedce into v1 Aug 16, 2021
@busunkim96 busunkim96 deleted the release-v1.31.2 branch August 16, 2021 20:53
@tseaver
Copy link
Contributor

tseaver commented Aug 16, 2021

@busunkim96 It looks like you were able to merge the PR even without the main Kokoro build completing: I believe that PR #241 actually dropped the branch protection for master

Update: oops,this is the v1 branch -- I'm not sure what branch protection rules should apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants