fix: Do not publish the protos to npm#8079
Merged
gcf-merge-on-green[bot] merged 3 commits intomainfrom Apr 20, 2026
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request removes the "build/protos" directory from the "files" array in the "package.json" files across a large number of Google Cloud Node.js client libraries. This change ensures that proto files are no longer included in the published npm packages. There are no review comments to address, and I have no feedback to provide.
danieljbruce
added
the
automerge
gcf-merge-on-green
bot
removed
the
automerge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This change solves googleapis/librarian#4820 and ensures that the .proto files don't get published to npm.
Impact
This just cleans up the built packages. It will make customer dependencies smaller which could improve the performance of their applications by shrinking their node_modules folders.
Testing
Only package.json files are modified in this change so tests against the source code aren't really required here.