Skip to content

chore: local OwlBot regeneration - #8641

Merged
feywind merged 2 commits into
googleapis:mainfrom
jskeet:local-owlbot-batch
Jun 15, 2026
Merged

chore: local OwlBot regeneration#8641
feywind merged 2 commits into
googleapis:mainfrom
jskeet:local-owlbot-batch

Conversation

@jskeet

@jskeet jskeet commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Performs OwlBot copying/post-processing on:

  • google-cloud-domains
  • grafeas

Note that in the grafeas commit, .readme-partials.yaml is removed as it was interfering with OwlBot post-processing.

@jskeet
jskeet requested a review from a team as a code owner June 15, 2026 10:59

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several Node.js client libraries, including google-cloud-capacityplanner, google-cloud-domains, google-monitoring-dashboard, and grafeas. Key updates include proto definition changes, dependency updates, and API surface adjustments, such as removing the CapacityPlanningService from the capacity planner package and adding risk and secret kind details to Grafeas. However, a critical issue was identified in the package.json files for both google-cloud-capacityplanner and google-monitoring-dashboard, where the package versions were incorrectly downgraded and the repository configurations were overwritten with standalone repository templates. These packages must be regenerated using the correct monorepo templates to preserve their metadata.

Comment thread packages/google-cloud-capacityplanner/package.json Outdated
Comment thread packages/google-monitoring-dashboard/package.json Outdated

@feywind feywind left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comments are almost entirely about READMEs, so I guess I'm okay with merging this one and coming back to fix templates later.

1. [Select or create a Cloud Platform project][projects].
1. [Enable billing for your project][billing].
1. [Enable the Cloud Domains API][enable_api].
1. [Enable the Cloud Domains API API][enable_api].

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't look correct.


| Sample | Source Code |
| --------------------------- | --------------------------------- |
| configure contact settings | [source code](https://github.com/googleapis/google-cloud-node/blob/main/packages/google-domains/samples/generated/v1/domains.configure_contact_settings.js) |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again on the lack of cloud shell links - is that on purpose?

@@ -1,3 +0,0 @@
introduction: |-
A [Grafeas API Client](https://grafeas.io/) compatible with Google Cloud's

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a fix for this in some other PR I probably can't find now. Just removing the apostrophe fixes it, so e.g. "the Google Cloud Container Analysis..."

[![npm version](https://img.shields.io/npm/v/@google-cloud/grafeas.svg)](https://www.npmjs.org/package/@google-cloud/grafeas)

Grafeas API client for Node.js
Container Analysis API client for Node.js

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks wrong.

[the CHANGELOG](https://github.com/googleapis/google-cloud-node/tree/main/packages/grafeas/CHANGELOG.md).
[the CHANGELOG][homepage_changelog].

* [Container Analysis API Nodejs Client API Reference](https://cloud.google.com/nodejs/docs/reference/grafeas/latest)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Likewise here, and the removed Grafeas links.


1. [Select or create a Cloud Platform project][projects].
1. [Enable the Grafeas API][enable_api].
1. [Enable billing for your project][billing].

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two lines also look weird.


| Sample | Source Code |
| --------------------------- | --------------------------------- |
| batch create notes | [source code](https://github.com/googleapis/google-cloud-node/blob/main/packages/grafeas/samples/generated/v1/grafeas.batch_create_notes.js) |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No Cloud Shell links.

| update occurrence | [source code](https://github.com/googleapis/google-cloud-node/blob/main/packages/grafeas/samples/generated/v1/grafeas.update_occurrence.js) |


The [Grafeas Node.js Client API Reference][client-docs] documentation

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this is related to the removal of the Grafeas links above.




This library is considered to be **stable**. The code surface will not change in backwards-incompatible ways

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's still stable, yeah?

@feywind
feywind merged commit 08b550f into googleapis:main Jun 15, 2026
32 checks passed
@jskeet
jskeet deleted the local-owlbot-batch branch July 8, 2026 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants