[pull] master from JuliaRegistries:master #49

pull · 2021-11-11T22:44:53Z

See Commits and Changes for more details.

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

google-cla · 2021-11-11T22:45:30Z

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-11T22:50:26Z

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-11T23:00:56Z

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-11T23:01:13Z

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-11T23:25:22Z

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-11T23:49: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-11-12T00:26: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.

google-cla · 2021-11-12T00:57:44Z

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-12T00:58: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.

google-cla · 2021-11-12T01:09:47Z

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-12T01:22:04Z

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-12T03:33:24Z

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-12T04:29:50Z

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-12T06:02:15Z

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-12T06:37: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.

google-cla · 2021-11-12T06:38:16Z

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-12T06:49:23Z

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-12T07:49:51Z

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-12T08:14:49Z

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-12T08:50:54Z

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-12T09:14:59Z

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-12T09:23:31Z

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-12T09:36:08Z

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-12T09:47:57Z

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-12T10:12: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-11-12T10:57:17Z

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-12T11:45:27Z

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-12T11:45: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-12T11:57:22Z

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.

UUID: 3c362404-f566-11ee-1572-e11a4b42c853 Repo: https://github.com/EnzymeAD/Reactant.jl.git Tree: 1a0655c26c0f090cf1e3ce175483069ec09d2731 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 1fb851c3-be98-478b-9657-166436d5cfc1 Repo: https://github.com/jherekhealy/CharFuncPricing.jl.git Tree: fe99bca04d5061469550025c4d8ae263baec1fd4 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 91bb5406-6c9a-523d-811d-0644c4229550 Repo: https://github.com/PetrKryslUCSD/FinEtools.jl.git Tree: dee40a36f9058886daba52a212beab7aa5c5bbd7 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: eff96d63-e80a-5855-80a2-b1b0885c5ab7 Repo: https://github.com/JuliaPhysics/Measurements.jl.git Tree: 3019b28107f63ee881f5883da916dd9b6aa294c1 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 932a18dc-bb55-4cd5-bdd6-1368ec9cea29 Repo: https://github.com/StellaOrg/ImplicitBVH.jl.git Tree: d4c5ce2af160ddf96b6636eea7ed8a10ead905c4 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 3a4d1b5c-c61d-41fd-a00a-5873ba7a1b0d Repo: https://github.com/CliMA/ClimaComms.jl.git Tree: 40ad44466dfe0092e18c04bc02c849fe8e095d30 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 2e771a56-c23a-4e0b-9282-20c2e37157e9 Repo: https://github.com/nsiccha/StanBlocks.jl.git Tree: 6177efba4c843073ef00ff76b6c34eaea93be259 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: c4671d76-df94-11ed-2057-43d4fd632fad Repo: https://github.com/kestrelquantum/Piccolo.jl.git Tree: afaadc2cb9da322bb9b9bf8cb35649729ca94693 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: ff71e718-51f3-5ec2-a782-8ffcbfa3c316 Repo: https://github.com/JuliaStats/MixedModels.jl.git Tree: 86ef59525a349a0b17e0efbfa957f52f9c676328 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 69f9d65-1b8b-4f14-83cd-52913e0d1f1c Repo: https://github.com/kaarthiksundar/GasTranSim.jl.git Tree: fe7aed721742910292052eb9b4a7ce82baee4d4d Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 0192cb87-2b54-54ad-80e0-3be72ad8a3c0 Repo: https://github.com/JuliaBinaryWrappers/Reactant_jll.jl.git Tree: d5e3d3d92cd367942ac5264f48a3098bcf89bdd5 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

UUID: 9f975960-e239-4209-8aa0-3d3ad5a82892 Repo: https://github.com/MurrellGroup/MolecularEvolution.jl.git Tree: 18ed4256e2661c0a39b7fb9ea84a3e1f467809de Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

Bumps [actions/stale](https://github.com/actions/stale) from 9.0.0 to 9.1.0. - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@28ca103...5bef64f) --- updated-dependencies: - dependency-name: actions/stale dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: DilumAluthge <[email protected]> Co-authored-by: Dilum Aluthge <[email protected]>

UUID: c82cd089-7bf7-41d7-976b-6b5d413cbe0a Repo: https://github.com/kleinhenz/SlurmClusterManager.jl.git Tree: c0a1feffb0b481a75f3f4b4de08a2b8584b52d9a Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: d89a494f-3841-4324-82bc-a003799788bd Repo: https://github.com/tz-lom/FunctionFusion.jl.git Tree: 1662115954e845fe14081e42da3e45be5dbc4487 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 9f975960-e239-4209-8aa0-3d3ad5a82892 Repo: https://github.com/MurrellGroup/MolecularEvolution.jl.git Tree: 7e89501d5209ebadc2b6b41564c196c60c329161 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: dce5fa8e-68ce-4431-a242-9469c69627a0 Repo: https://github.com/gaelforget/MITgcm.jl.git Tree: 63831a972c6944c03baddef07e79ba4568a9855d Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: fe5ef43c-4912-423d-9170-4bd5cb6a013a Repo: https://github.com/paulxshen/ArrayPadding.jl.git Tree: 0e65ddd756047cc06214a18d23a2dc841aac1ff0 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8 Co-authored-by: JuliaHubRegistrator <[email protected]>

UUID: 46e5285b-ff06-5712-adf2-cc145d39f096 Repo: https://github.com/JuliaBinaryWrappers/PaStiX_jll.jl.git Tree: 8fea8900e7286b21ee2dce419ca1fa0fe8e59de5 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

UUID: 86993f9b-bbba-4084-97c5-ee15961ad48b Repo: https://github.com/TidierOrg/TidierDB.jl.git Tree: 16e3a0dd847a03c81ee7e733c38781e9266accfe Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: f6adb021-9183-4f40-84dc-8cea6f651bb0 Repo: https://github.com/gaelforget/ClimateModels.jl.git Tree: 57a75abae974e07d74467a990855995f4128e6f2 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 06919feb-fec6-4e74-a260-ddb603bc7a1b Repo: https://gitlab.com/nsajko/TypeDomainNaturalNumbers.jl.git Tree: fa119fbebd1461150c9519b6f40357dfd050c320 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8 Co-authored-by: JuliaHubRegistrator <[email protected]>

UUID: 4ee394cb-3365-5eb0-8335-949819d2adfc Repo: https://github.com/JuliaBinaryWrappers/CUDA_Driver_jll.jl.git Tree: 7cc4ec34bbd15c0381ed0d81b28efed3027c7bca Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

UUID: f4abf1af-0426-5881-a0da-e2f168889b5e Repo: https://github.com/JuliaAlgebra/MultivariateMoments.jl.git Tree: 6145821fbe39bcaa368430d0476f6ff5c66c49c7 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 763ebaa8-b0d2-5f6b-90ef-4fc23b5db1c4 Repo: https://github.com/JuliaBinaryWrappers/MAGEMin_jll.jl.git Tree: cf24a088a6fdc59f95696de44e7670fbd13adece Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

UUID: b54e767b-1ebd-4480-ac2a-f5f4d8853074 Repo: https://github.com/unfoldtoolbox/UnfoldBIDS.jl.git Tree: 3ff54fe8d28727101f0eac335b111cd0892626c0 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

UUID: 6cbf2f2e-7e60-5632-ac76-dca2274e0be0 Repo: https://github.com/JuliaBinaryWrappers/CUDA_SDK_jll.jl.git Tree: c3daec92879eb395120d90e581a53eac5a119b49 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

UUID: e5d170eb-415a-4524-987b-12f1bce1ddab Repo: https://github.com/ComputationalThermodynamics/MAGEMin_C.jl.git Tree: e39e765b04666345fdccac0876869e274389e502 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8 Co-authored-by: JuliaHubRegistrator <[email protected]>

UUID: ad7bff83-59f0-4382-9fe5-c2ac8aa77434 Repo: https://github.com/Klafyvel/REPLSmuggler.jl.git Tree: 23f942af20f7a55e91d8d67f9789e3ad6fc7637b Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

pull bot added the ⤵️ pull label Nov 11, 2021

Registrator and others added 30 commits January 26, 2025 13:02

New version: Reactant v0.2.22 (#123757)

cd1a7af

UUID: 3c362404-f566-11ee-1572-e11a4b42c853 Repo: https://github.com/EnzymeAD/Reactant.jl.git Tree: 1a0655c26c0f090cf1e3ce175483069ec09d2731 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: CharFuncPricing v0.4.1 (#123755)

433d834

UUID: 1fb851c3-be98-478b-9657-166436d5cfc1 Repo: https://github.com/jherekhealy/CharFuncPricing.jl.git Tree: fe99bca04d5061469550025c4d8ae263baec1fd4 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: FinEtools v8.0.27 (#123758)

e214d04

UUID: 91bb5406-6c9a-523d-811d-0644c4229550 Repo: https://github.com/PetrKryslUCSD/FinEtools.jl.git Tree: dee40a36f9058886daba52a212beab7aa5c5bbd7 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: Measurements v2.12.0 (#123759)

66aa8ce

UUID: eff96d63-e80a-5855-80a2-b1b0885c5ab7 Repo: https://github.com/JuliaPhysics/Measurements.jl.git Tree: 3019b28107f63ee881f5883da916dd9b6aa294c1 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: ImplicitBVH v0.5.1 (#123760)

1d99b40

UUID: 932a18dc-bb55-4cd5-bdd6-1368ec9cea29 Repo: https://github.com/StellaOrg/ImplicitBVH.jl.git Tree: d4c5ce2af160ddf96b6636eea7ed8a10ead905c4 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: ClimaComms v0.6.6 (#123761)

f41940d

UUID: 3a4d1b5c-c61d-41fd-a00a-5873ba7a1b0d Repo: https://github.com/CliMA/ClimaComms.jl.git Tree: 40ad44466dfe0092e18c04bc02c849fe8e095d30 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New package: StanBlocks v0.1.0 (#123594)

63977b2

UUID: 2e771a56-c23a-4e0b-9282-20c2e37157e9 Repo: https://github.com/nsiccha/StanBlocks.jl.git Tree: 6177efba4c843073ef00ff76b6c34eaea93be259 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: Piccolo v0.5.0 (#123762)

a3d7e48

UUID: c4671d76-df94-11ed-2057-43d4fd632fad Repo: https://github.com/kestrelquantum/Piccolo.jl.git Tree: afaadc2cb9da322bb9b9bf8cb35649729ca94693 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: MixedModels v4.30.0 (#123764)

8d31f04

UUID: ff71e718-51f3-5ec2-a782-8ffcbfa3c316 Repo: https://github.com/JuliaStats/MixedModels.jl.git Tree: 86ef59525a349a0b17e0efbfa957f52f9c676328 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: GasTranSim v0.2.2 (#123765)

1c9b161

UUID: 69f9d65-1b8b-4f14-83cd-52913e0d1f1c Repo: https://github.com/kaarthiksundar/GasTranSim.jl.git Tree: fe7aed721742910292052eb9b4a7ce82baee4d4d Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: Reactant_jll v0.0.54+0 (#123766)

48ae00a

UUID: 0192cb87-2b54-54ad-80e0-3be72ad8a3c0 Repo: https://github.com/JuliaBinaryWrappers/Reactant_jll.jl.git Tree: d5e3d3d92cd367942ac5264f48a3098bcf89bdd5 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

New version: MolecularEvolution v0.2.2 (#123767)

d4267c1

UUID: 9f975960-e239-4209-8aa0-3d3ad5a82892 Repo: https://github.com/MurrellGroup/MolecularEvolution.jl.git Tree: 18ed4256e2661c0a39b7fb9ea84a3e1f467809de Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

🤖 Update one or more manifest files in the .ci directory (#123769)

2697807

Co-authored-by: DilumAluthge <[email protected]> Co-authored-by: Dilum Aluthge <[email protected]>

New version: SlurmClusterManager v0.1.4 (#123770)

f2ca81e

UUID: c82cd089-7bf7-41d7-976b-6b5d413cbe0a Repo: https://github.com/kleinhenz/SlurmClusterManager.jl.git Tree: c0a1feffb0b481a75f3f4b4de08a2b8584b52d9a Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: FunctionFusion v0.1.3 (#123771)

c2bcbce

UUID: d89a494f-3841-4324-82bc-a003799788bd Repo: https://github.com/tz-lom/FunctionFusion.jl.git Tree: 1662115954e845fe14081e42da3e45be5dbc4487 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: MolecularEvolution v0.2.3 (#123772)

4ea54bd

UUID: 9f975960-e239-4209-8aa0-3d3ad5a82892 Repo: https://github.com/MurrellGroup/MolecularEvolution.jl.git Tree: 7e89501d5209ebadc2b6b41564c196c60c329161 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: MITgcm v0.5.1 (#123773)

54d3ebf

UUID: dce5fa8e-68ce-4431-a242-9469c69627a0 Repo: https://github.com/gaelforget/MITgcm.jl.git Tree: 63831a972c6944c03baddef07e79ba4568a9855d Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: PaStiX_jll v6.4.0+0 (#123776)

9d1ed3e

UUID: 46e5285b-ff06-5712-adf2-cc145d39f096 Repo: https://github.com/JuliaBinaryWrappers/PaStiX_jll.jl.git Tree: 8fea8900e7286b21ee2dce419ca1fa0fe8e59de5 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

New version: TidierDB v0.7.0 (#123777)

c408bf8

UUID: 86993f9b-bbba-4084-97c5-ee15961ad48b Repo: https://github.com/TidierOrg/TidierDB.jl.git Tree: 16e3a0dd847a03c81ee7e733c38781e9266accfe Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: ClimateModels v0.3.7 (#123778)

3628923

UUID: f6adb021-9183-4f40-84dc-8cea6f651bb0 Repo: https://github.com/gaelforget/ClimateModels.jl.git Tree: 57a75abae974e07d74467a990855995f4128e6f2 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: CUDA_Driver_jll v0.12.0+0 (#123780)

c6e96f4

UUID: 4ee394cb-3365-5eb0-8335-949819d2adfc Repo: https://github.com/JuliaBinaryWrappers/CUDA_Driver_jll.jl.git Tree: 7cc4ec34bbd15c0381ed0d81b28efed3027c7bca Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

New version: MultivariateMoments v0.4.10 (#123781)

4ae061a

UUID: f4abf1af-0426-5881-a0da-e2f168889b5e Repo: https://github.com/JuliaAlgebra/MultivariateMoments.jl.git Tree: 6145821fbe39bcaa368430d0476f6ff5c66c49c7 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: MAGEMin_jll v1.6.6+0 (#123782)

856743c

UUID: 763ebaa8-b0d2-5f6b-90ef-4fc23b5db1c4 Repo: https://github.com/JuliaBinaryWrappers/MAGEMin_jll.jl.git Tree: cf24a088a6fdc59f95696de44e7670fbd13adece Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

New version: UnfoldBIDS v0.3.1 (#123783)

f87bb61

UUID: b54e767b-1ebd-4480-ac2a-f5f4d8853074 Repo: https://github.com/unfoldtoolbox/UnfoldBIDS.jl.git Tree: 3ff54fe8d28727101f0eac335b111cd0892626c0 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

New version: CUDA_SDK_jll v12.8.0+0 (#123785)

776fa71

UUID: 6cbf2f2e-7e60-5632-ac76-dca2274e0be0 Repo: https://github.com/JuliaBinaryWrappers/CUDA_SDK_jll.jl.git Tree: c3daec92879eb395120d90e581a53eac5a119b49 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8

New version: REPLSmuggler v0.6.0 (#123787)

dd42bda

UUID: ad7bff83-59f0-4382-9fe5-c2ac8aa77434 Repo: https://github.com/Klafyvel/REPLSmuggler.jl.git Tree: 23f942af20f7a55e91d8d67f9789e3ad6fc7637b Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[pull] master from JuliaRegistries:master #49

[pull] master from JuliaRegistries:master #49

pull bot commented Nov 11, 2021 •

edited

Loading

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 11, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 12, 2021

[pull] master from JuliaRegistries:master #49

Are you sure you want to change the base?

[pull] master from JuliaRegistries:master #49

Conversation

pull bot commented Nov 11, 2021 • edited Loading

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

pull bot commented Nov 11, 2021 •

edited

Loading