Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(all): auto-regenerate gapics #4770

Merged
merged 4 commits into from
Sep 20, 2021
Merged

chore(all): auto-regenerate gapics #4770

merged 4 commits into from
Sep 20, 2021

Conversation

yoshi-automation
Copy link
Contributor

This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

  • Ensure that the version of genproto in go.mod has been updated.
  • Ensure that CI is passing. If it's failing, it requires your manual attention.
  • Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#677

Changes:

feat(contactcenterinsights): filter is used to filter conversations used for issue model training feat: update_time is used to indicate when the phrase matcher was updated
PiperOrigin-RevId: 397164390
Source-Link: googleapis/googleapis@2ec8242

yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Sep 17, 2021
@yoshi-automation
chore(all): auto-regenerate .pb.go files
724f49e 
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4770

Changes:

chore: regenerate API index

  Source-Link: googleapis/googleapis@0f360f0

feat: publish cloud/sql/v1 artifacts
  PiperOrigin-RevId: 397185811
  Source-Link: googleapis/googleapis@ea09b65

feat(contactcenterinsights): filter is used to filter conversations used for issue model training feat: update_time is used to indicate when the phrase matcher was updated
  PiperOrigin-RevId: 397164390
  Source-Link: googleapis/googleapis@2ec8242

chore: regenerate API index

  Source-Link: googleapis/googleapis@cce61a9

feat: Publish Google Cloud Deploy v1 API
  PiperOrigin-RevId: 397120018
  Source-Link: googleapis/googleapis@3d1ce71

chore: regenerate API index

  Source-Link: googleapis/googleapis@48d9fb8

chore(googleads)!: remove protos for v6, which has sunset
  Committer: @aohren

  BREAKING CHANGE: Removing the entire version 6 of the API because it has sunset and is no longer in use.

  PiperOrigin-RevId: 397044375
  Source-Link: googleapis/googleapis@4bde293
@yoshi-automation yoshi-automation mentioned this pull request Sep 17, 2021
Merged
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Sep 17, 2021
@snippet-bot
Copy link

snippet-bot bot commented Sep 17, 2021 •
edited
Loading

Here is the summary of possible violations 😱

There are 48 possible violations for not having product prefix.

The end of the violation section. All the stuff below is FYI purposes only.

Here is the summary of changes.

You are about to add 126 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

codyoss pushed a commit to googleapis/go-genproto that referenced this pull request Sep 17, 2021
@yoshi-automation
chore(all): auto-regenerate .pb.go files (#677)
b395a37 
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4770

Changes:

chore: regenerate API index

  Source-Link: googleapis/googleapis@0f360f0

feat: publish cloud/sql/v1 artifacts
  PiperOrigin-RevId: 397185811
  Source-Link: googleapis/googleapis@ea09b65

feat(contactcenterinsights): filter is used to filter conversations used for issue model training feat: update_time is used to indicate when the phrase matcher was updated
  PiperOrigin-RevId: 397164390
  Source-Link: googleapis/googleapis@2ec8242

chore: regenerate API index

  Source-Link: googleapis/googleapis@cce61a9

feat: Publish Google Cloud Deploy v1 API
  PiperOrigin-RevId: 397120018
  Source-Link: googleapis/googleapis@3d1ce71

chore: regenerate API index

  Source-Link: googleapis/googleapis@48d9fb8

chore(googleads)!: remove protos for v6, which has sunset
  Committer: @aohren

  BREAKING CHANGE: Removing the entire version 6 of the API because it has sunset and is no longer in use.

  PiperOrigin-RevId: 397044375
  Source-Link: googleapis/googleapis@4bde293
@yoshi-automation
chore(all): auto-regenerate gapics
6d2e145 
This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

- Ensure that the version of genproto in go.mod has been updated.
- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#677

Changes:

feat(contactcenterinsights): filter is used to filter conversations used for issue model training feat: update_time is used to indicate when the phrase matcher was updated
  PiperOrigin-RevId: 397164390
  Source-Link: googleapis/googleapis@2ec8242
@yoshi-automation yoshi-automation marked this pull request as ready for review September 17, 2021 15:04
@yoshi-automation yoshi-automation requested a review from a team September 17, 2021 15:04
@yoshi-automation yoshi-automation requested review from a team as code owners September 17, 2021 15:04
@codyoss codyoss added kokoro:force-run Add this label to force Kokoro to re-run the tests. automerge Merge the pull request once unit tests and other checks pass. labels Sep 17, 2021
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 17, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 17, 2021
@codyoss codyoss added the automerge Merge the pull request once unit tests and other checks pass. label Sep 20, 2021
@google-cla
Copy link

google-cla bot commented Sep 20, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 20, 2021
@google-cla
Copy link

google-cla bot commented Sep 20, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 20, 2021
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 20, 2021
@google-cla
Copy link

google-cla bot commented Sep 20, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 20, 2021
@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. automerge Merge the pull request once unit tests and other checks pass. and removed cla: no This human has *not* signed the Contributor License Agreement. automerge Merge the pull request once unit tests and other checks pass. labels Sep 20, 2021
@google-cla
Copy link

google-cla bot commented Sep 20, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 20, 2021
@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 20, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit cb3a823 into master Sep 20, 2021
@gcf-merge-on-green gcf-merge-on-green bot deleted the regen_gocloud branch September 20, 2021 23:58
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@codyoss codyoss codyoss approved these changes

@crwilcox crwilcox Awaiting requested review from crwilcox

@hengfengli hengfengli Awaiting requested review from hengfengli

@skuruppu skuruppu Awaiting requested review from skuruppu

@tritone tritone Awaiting requested review from tritone

@loferris loferris Awaiting requested review from loferris

Assignees
No one assigned
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@yoshi-automation @codyoss @kokoro-team