[pull] main from actions:main by pull[bot] · Pull Request #3 · dgfug/python-versions

pull · 2021-10-13T12:26:40Z

See Commits and Changes for more details.

Can you help keep this open source service alive? 💖 Please sponsor : )

Remove Ubuntu 16.04 from images

google-cla · 2021-10-13T12:26: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.

Remove Ubuntu 16.04 from pipeline

google-cla · 2021-10-14T08:37:34Z

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-10-14T13:56:53Z

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.

…#117)

google-cla · 2021-10-18T11:37:35Z

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.

Co-authored-by: Service account <[email protected]>

google-cla · 2021-10-19T12:34:45Z

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.

[versions-manifest] Update for release from 11/06/2021

google-cla · 2021-11-06T08:03:43Z

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-11-16T06:55:01Z

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.

[versions-manifest] Update for release from 12/14/2021

Skip sqlite module test for python3.11.0-alpha.3

…ration Migrate macOS pipelines to macOS-10.15

[versions-manifest] Update for release from 12/22/2021

Migrate windows pipelines to windows-2019

Co-authored-by: Service account <[email protected]>

…thon-builder Add ability to choose platform to build Python

[versions-manifest] Update for release from 03/17/2022

[versions-manifest] Update for release from 03/19/2022

[versions-manifest] Update for release from 03/21/2022

[versions-manifest] Update for release from 03/24/2022

Vladimir Safonkin and others added 2 commits October 12, 2021 16:10

Remove Ubuntu 16.04 from images

6b02f07

Merge pull request #120 from vsafonkin/v-vlsafo/remove-ubuntu-16.04

33626e4

Remove Ubuntu 16.04 from images

step-security Bot mentioned this pull request Oct 13, 2021

Secure workflows in pull request #3 #4

Open

pull Bot added the ⤵️ pull label Oct 13, 2021

MaksimZhukov added 2 commits October 14, 2021 10:59

Update build-python-packages.yml

c188065

Merge pull request #122 from actions/remove-ubuntu16

a0626d7

Remove Ubuntu 16.04 from pipeline

Uptake of the latest changes for helpers submodule (#121)

cd4aab3

When upgrading pip, don't warn there's a new version of pip available (…

641a276

…#117)

Update versions-manifest (#123)

6f2b7dc

Co-authored-by: Service account <[email protected]>

459680 and others added 2 commits November 6, 2021 08:02

Update versions-manifest

d5c09cb

Merge pull request #125 from actions/update-versions-manifest-file

71d75d7

[versions-manifest] Update for release from 11/06/2021

Update versions-manifest (#126)

2e89c64

459680 and others added 11 commits December 14, 2021 13:26

Update versions-manifest

1a5414f

Merge pull request #127 from actions/update-versions-manifest-file

5aa825b

[versions-manifest] Update for release from 12/14/2021

Skip sqlite module test for python3.11

1499930

Merge pull request #129 from actions/python3.11_sqlite

9e322ab

Skip sqlite module test for python3.11.0-alpha.3

Migrate macOS pipelines to macOS-10.15

e9b568c

Merge pull request #128 from actions/v-mkoliada/clean_macos-10.15_mig…

63966c6

…ration Migrate macOS pipelines to macOS-10.15

Update versions-manifest

79fa4f7

Merge pull request #130 from actions/update-versions-manifest-file

71d3f7d

[versions-manifest] Update for release from 12/22/2021

Migrate windows pipelines to windows-2019

026f6eb

Merge pull request #131 from actions/v-mkoliada/switch_to_win2019

c310309

Migrate windows pipelines to windows-2019

Migrate python-versions pipeline to GH Actions

59e54b2

github-actions Bot and others added 29 commits January 27, 2022 10:54

Update versions-manifest (#138)

b275162

Co-authored-by: Service account <[email protected]>

Update versions-manifest (#139)

8cfdc61

Co-authored-by: Service account <[email protected]>

Update versions-manifest (#140)

210583e

Co-authored-by: Service account <[email protected]>

Update versions-manifest (#141)

797eb71

Co-authored-by: Service account <[email protected]>

Add ability to choose platform to build Python

3ec6c98

Update generate_matrix job to allow execution via PR

588fb9d

Minor corrections according to comments

044e281

Adding python-versions-runner workflow (#137)

e74fccf

Merge pull request #143 from nikolai-frolov/users/v-nfrolov/update-py…

79e9e3b

…thon-builder Add ability to choose platform to build Python

Remove AzDo related code (#144)

ba3a558

Update versions-manifest

0cbb516

Merge pull request #142 from actions/update-versions-manifest-file

cd04e6b

[versions-manifest] Update for release from 03/17/2022

Update versions-manifest

2552b10

Merge pull request #146 from actions/update-versions-manifest-file

386cf09

[versions-manifest] Update for release from 03/17/2022

Update versions-manifest

ce7d569

Merge pull request #147 from actions/update-versions-manifest-file

3d1cc99

[versions-manifest] Update for release from 03/19/2022

Update versions-manifest

153004c

Merge pull request #148 from actions/update-versions-manifest-file

b4ee3eb

[versions-manifest] Update for release from 03/21/2022

Update versions-manifest

cf55c35

Merge pull request #149 from actions/update-versions-manifest-file

8bea4cf

[versions-manifest] Update for release from 03/21/2022

Update versions-manifest

ce8fa50

Merge pull request #150 from actions/update-versions-manifest-file

78b21b7

[versions-manifest] Update for release from 03/21/2022

Update versions-manifest

daf0a68

Merge pull request #151 from actions/update-versions-manifest-file

5ce03b9

[versions-manifest] Update for release from 03/24/2022

Update versions-manifest

cda7fd9

Merge pull request #152 from actions/update-versions-manifest-file

5f1fbb8

[versions-manifest] Update for release from 03/24/2022

Update versions-manifest

18aeba4

Merge branch 'main' into update-versions-manifest-file

769f682

Merge pull request #153 from actions/update-versions-manifest-file

7e0253f

[versions-manifest] Update for release from 03/24/2022

pull Bot merged commit 7e0253f into dgfug:main Mar 29, 2022

Navigation Menu

Repository navigation

[pull] main from actions:main - #3

[pull] main from actions:main#3
pull[bot] merged 65 commits into
dgfug:mainfrom
actions:main

pull Bot commented Oct 13, 2021 •

edited

Loading

Uh oh!

google-cla Bot commented Oct 13, 2021

Uh oh!

google-cla Bot commented Oct 14, 2021

Uh oh!

google-cla Bot commented Oct 14, 2021

Uh oh!

google-cla Bot commented Oct 18, 2021

Uh oh!

google-cla Bot commented Oct 19, 2021

Uh oh!

google-cla Bot commented Nov 6, 2021

Uh oh!

google-cla Bot commented Nov 16, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

Conversation

pull Bot commented Oct 13, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

google-cla Bot commented Oct 13, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Oct 14, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Oct 14, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Oct 18, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Oct 19, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 6, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla Bot commented Nov 16, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

pull Bot commented Oct 13, 2021 •

edited

Loading