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.

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

chore(all): auto-regenerate gapics #4966

Merged
merged 5 commits into from
Oct 11, 2021
Merged

chore(all): auto-regenerate gapics #4966

merged 5 commits into from
Oct 11, 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#695

Changes:

feat(monitoring/apiv3): add CreateServiceTimeSeries RPC
PiperOrigin-RevId: 401594069
Source-Link: googleapis/googleapis@3b9c98e

yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Oct 8, 2021
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#4966

Changes:

chore: regenerate API index

  Source-Link: googleapis/googleapis@94f7778

feat(monitoring/apiv3): add CreateServiceTimeSeries RPC
  PiperOrigin-RevId: 401594069
  Source-Link: googleapis/googleapis@3b9c98e

fix: add a dummy change 1 at the v1beta2 for testing release messages with commit body
  commit body

  PiperOrigin-RevId: 401572985
  Source-Link: googleapis/googleapis@14a959f

fix!: add a dummy change 2 at the v1 for testing release messages with commit body
  commit body 1
  commit body 2

  ---
  fix: add a dummy change 1 at the v1 for testing release messages without commit body

  ---
  chore!: add a dummy change 3 at the v1main for testing release messages without commit body

  ---
  build(lang)!: add a dummy change 2 at the v1main for testing release messages with commit body

  commit body1
  commit body2

  ---
  fix(lang)!: add a dummy change 1 at the v1main for testing release messages with commit body

  PiperOrigin-RevId: 401572983
  Source-Link: googleapis/googleapis@528b839

chore!: add a dummy change 3 at the v1main for testing release messages without commit body
  ---
  build(lang)!: add a dummy change 2 at the v1main for testing release messages with commit body

  commit body1
  commit body2

  ---
  fix(lang)!: add a dummy change 1 at the v1main for testing release messages with commit body

  PiperOrigin-RevId: 401572974
  Source-Link: googleapis/googleapis@b21bb45

fix: add a dummy change 1 at the v1beta1 for testing release messages without commit body
  PiperOrigin-RevId: 401572962
  Source-Link: googleapis/googleapis@485bf01

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401566570
  Source-Link: googleapis/googleapis@5d88c6b

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401566558
  Source-Link: googleapis/googleapis@614dfd7

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419143
  Source-Link: googleapis/googleapis@d4d09eb

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419136
  Source-Link: googleapis/googleapis@50d96dc

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419128
  Source-Link: googleapis/googleapis@99ec928
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Oct 8, 2021
@snippet-bot
Copy link

snippet-bot bot commented Oct 8, 2021

Here is the summary of changes.

You are about to add 4 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 Oct 8, 2021
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#4966

Changes:

chore: regenerate API index

  Source-Link: googleapis/googleapis@94f7778

feat(monitoring/apiv3): add CreateServiceTimeSeries RPC
  PiperOrigin-RevId: 401594069
  Source-Link: googleapis/googleapis@3b9c98e

fix: add a dummy change 1 at the v1beta2 for testing release messages with commit body
  commit body

  PiperOrigin-RevId: 401572985
  Source-Link: googleapis/googleapis@14a959f

fix!: add a dummy change 2 at the v1 for testing release messages with commit body
  commit body 1
  commit body 2

  ---
  fix: add a dummy change 1 at the v1 for testing release messages without commit body

  ---
  chore!: add a dummy change 3 at the v1main for testing release messages without commit body

  ---
  build(lang)!: add a dummy change 2 at the v1main for testing release messages with commit body

  commit body1
  commit body2

  ---
  fix(lang)!: add a dummy change 1 at the v1main for testing release messages with commit body

  PiperOrigin-RevId: 401572983
  Source-Link: googleapis/googleapis@528b839

chore!: add a dummy change 3 at the v1main for testing release messages without commit body
  ---
  build(lang)!: add a dummy change 2 at the v1main for testing release messages with commit body

  commit body1
  commit body2

  ---
  fix(lang)!: add a dummy change 1 at the v1main for testing release messages with commit body

  PiperOrigin-RevId: 401572974
  Source-Link: googleapis/googleapis@b21bb45

fix: add a dummy change 1 at the v1beta1 for testing release messages without commit body
  PiperOrigin-RevId: 401572962
  Source-Link: googleapis/googleapis@485bf01

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401566570
  Source-Link: googleapis/googleapis@5d88c6b

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401566558
  Source-Link: googleapis/googleapis@614dfd7

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419143
  Source-Link: googleapis/googleapis@d4d09eb

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419136
  Source-Link: googleapis/googleapis@50d96dc

Synchronize new proto/yaml changes.
  PiperOrigin-RevId: 401419128
  Source-Link: googleapis/googleapis@99ec928
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#695

Changes:

feat(monitoring/apiv3): add CreateServiceTimeSeries RPC
  PiperOrigin-RevId: 401594069
  Source-Link: googleapis/googleapis@3b9c98e
@yoshi-automation yoshi-automation marked this pull request as ready for review October 8, 2021 15:06
@yoshi-automation yoshi-automation requested a review from a team as a code owner October 8, 2021 15:06
@google-cla
Copy link

google-cla bot commented Oct 8, 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 Oct 8, 2021
@codyoss codyoss added automerge Merge the pull request once unit tests and other checks pass. cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Oct 8, 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 Oct 8, 2021
@google-cla
Copy link

google-cla bot commented Oct 11, 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 the automerge Merge the pull request once unit tests and other checks pass. label Oct 11, 2021
@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 Oct 11, 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 Oct 11, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit 9e41088 into master Oct 11, 2021
@gcf-merge-on-green gcf-merge-on-green bot deleted the regen_gocloud branch October 11, 2021 16:04
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants