Skip to content

chore: example changes from Release Please files by Librarian#8777

Draft
suztomo wants to merge 1 commit into
googleapis:mainfrom
suztomo:before-agentregistry
Draft

chore: example changes from Release Please files by Librarian#8777
suztomo wants to merge 1 commit into
googleapis:mainfrom
suztomo:before-agentregistry

Conversation

@suztomo

@suztomo suztomo commented Jun 29, 2026

Copy link
Copy Markdown
Member

These changes come from "librarian add" command with the enhancement
of managing Release Please files by Librarian.

suztomo@suztomo:~/librarian-2026/librarian$ go build  -o /tmp/librarian ./cmd/librarian
suztomo@suztomo:~/librarian-2026/librarian$ cd ../google-cloud-node
suztomo@suztomo:~/librarian-2026/google-cloud-node$ git checkout -b before-agentregistry 51f4a308226ea49ed234b01211413a1d2732de24
suztomo@suztomo:~/librarian-2026/google-cloud-node$ /tmp/librarian add google/cloud/agentregistry/v1

51f4a30 was the parent commit of
the commit that added the agentregistry package in google-cloud-node.

@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 reorganizes and alphabetizes package definitions across release configuration files, adds the new library google-cloud-agentregistry, and removes unused mixins configurations from several libraries in librarian.yaml. Feedback is provided regarding the missing version field for the newly added google-cloud-agentregistry library in librarian.yaml to ensure consistency with other definitions.

Comment thread librarian.yaml
Comment on lines +195 to +196
- name: google-cloud-agentregistry
apis:

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.

medium

The new library google-cloud-agentregistry is missing the version field. To maintain consistency with other library definitions in this file, please add the version field matching the 0.0.0 version specified in .release-please-manifest.json.

  - name: google-cloud-agentregistry
    version: 0.0.0
    apis:

@suztomo suztomo force-pushed the before-agentregistry branch from e466b2f to bdd87d7 Compare June 29, 2026 20:22
These changes come from "librarian add" command with the enhancement
of managing Release Please files by Librarian.

```
suztomo@suztomo:~/librarian-2026/librarian$ go build  -o /tmp/librarian ./cmd/librarian
suztomo@suztomo:~/librarian-2026/librarian$ cd ../google-cloud-node
suztomo@suztomo:~/librarian-2026/google-cloud-node$ git checkout -b before-agentregistry 51f4a30
suztomo@suztomo:~/librarian-2026/google-cloud-node$ /tmp/librarian add google/cloud/agentregistry/v1
```

51f4a30 was the parent commit of
the commit that added the agentregistry package in google-cloud-node.
@suztomo suztomo force-pushed the before-agentregistry branch from bdd87d7 to 33ff142 Compare June 29, 2026 20:23
suztomo added a commit to googleapis/librarian that referenced this pull request Jun 30, 2026
We had to manally add Release Please entry in the configuration files
when we onboard a new library to google-cloud-node.
googleapis/google-cloud-node#8693 is the
example. Let's have Librarian to add the entries in the Release Please
files.

Python and Go already have the feature with the "bulk" files. Let's make
the logic work for google-cloud-node's configuration files. They use the
default names: release-please-config.json and
.release-please-manifest.json.

Note that when Librarian starts to touch the Release Please files, it
sorts the JSON keys.
googleapis/google-cloud-node#8777 is the outcome
of an example invocation for the agentregistry package using the source
tree before the package was introduced. The JSON keys are sorted. (The
irrelevant changes in the mixin fields are due to recent change in
Librarian for NodeJS.)

Fixes #6528
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.

1 participant