chore: release 0.2.0 by github-actions[bot] · Pull Request #104 · GoogleCloudPlatform/cloud-sql-python-connector

github-actions · 2021-05-14T17:11:44Z

🤖 I have created a release beep boop

0.2.0 (2021-06-01)

Features

add support for IAM auth with pg8000 driver (#101) (6703232)

Bug Fixes

force use of TLSv1.3 when IAM auth enabled (#108) (a10aa5a)

This PR was generated with Release Please. See documentation.

google-cla · 2021-05-14T17:11:48Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-05-18T22:20:02Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-05-20T14:30:33Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-05-24T19:08:25Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-05-26T08:01:07Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-06-01T15:53:36Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

github-actions Bot added the autorelease: pending Release please needs to do its work on this. label May 14, 2021

blunderbuss-gcf Bot assigned shubha-rajan May 14, 2021

google-cla Bot added the cla: no label May 14, 2021

github-actions Bot force-pushed the release-v0.2.0 branch from 6c91113 to 2e375cf Compare May 18, 2021 22:19

github-actions Bot force-pushed the release-v0.2.0 branch from 2e375cf to 1d1e54d Compare May 20, 2021 14:30

github-actions Bot force-pushed the release-v0.2.0 branch from 1d1e54d to 6e9c07c Compare May 24, 2021 19:08

github-actions Bot force-pushed the release-v0.2.0 branch from 6e9c07c to 925ce1c Compare May 26, 2021 08:01

chore: release 0.2.0

b7833db

github-actions Bot force-pushed the release-v0.2.0 branch from 925ce1c to b7833db Compare June 1, 2021 15:53

shubha-rajan added cla: yes and removed cla: no labels Jun 1, 2021

kokoro-team removed the kokoro:force-run label Jun 1, 2021

shubha-rajan approved these changes Jun 1, 2021

View reviewed changes

shubha-rajan merged commit 1e7befd into main Jun 1, 2021

shubha-rajan deleted the release-v0.2.0 branch June 1, 2021 21:21

shubha-rajan added autorelease: tagged Release please has completed a release for this. and removed autorelease: pending Release please needs to do its work on this. labels Jun 1, 2021

jackwotherspoon removed the autorelease: tagged Release please has completed a release for this. label Jul 22, 2022

Navigation Menu

Uh oh!

chore: release 0.2.0 - #104

chore: release 0.2.0#104
shubha-rajan merged 1 commit into
mainfrom
release-v0.2.0

github-actions Bot commented May 14, 2021 •

edited

Loading

Uh oh!

google-cla Bot commented May 14, 2021

Uh oh!

google-cla Bot commented May 18, 2021

Uh oh!

google-cla Bot commented May 20, 2021

Uh oh!

google-cla Bot commented May 24, 2021

Uh oh!

google-cla Bot commented May 26, 2021

Uh oh!

google-cla Bot commented Jun 1, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

github-actions Bot commented May 14, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 I have created a release *beep* *boop*

0.2.0 (2021-06-01)

Features

Bug Fixes

Uh oh!

google-cla Bot commented May 14, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented May 18, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented May 20, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented May 24, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented May 26, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Jun 1, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

github-actions Bot commented May 14, 2021 •

edited

Loading

🤖 I have created a release beep boop