Conversation
…ating throgh history
chingor13
requested changes
Feb 18, 2026
Contributor
chingor13
left a comment
There was a problem hiding this comment.
Can you add this to the manifest config json schema in schemas/?
Otherwise, LGTM
Contributor
Sorry, |
chingor13
approved these changes
Feb 18, 2026
colebanderson8392-arch
approved these changes
Feb 21, 2026
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
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.
Release please has been consistently failing on google-cloud-node repo due to 502 errors when trying to run this query. The only way to actually have it succeed was to update the number of commits per request to be 1. We don't want to make this change for all clients as it will slow down release please run time, so lets make it configurable so node can set it to a low value.