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

fix(deps): update dependency @grpc/grpc-js to ~1.10.0 #1558

Merged

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Feb 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@grpc/grpc-js (source) ~1.9.6 -> ~1.10.0 age adoption passing confidence

Release Notes

grpc/grpc-node (@​grpc/grpc-js)

v1.10.0: @​grpc/grpc-js 1.10.0

Compare Source

Changelog

Experimental API Changes

  • Added:
    • Endpoint
    • endpointToString
    • endpointHasAddress
    • LeafLoadBalancer
    • HealthListener
    • SubchannelInterface#isHealthy
    • SubchannelInterface#addHealthStateWatcher
    • SubchannelInterface#removeHealthStateWatcher
    • SubchannelWrapper#setHealthy
    • selectLbConfigFromList
    • parseLoadBalancingConfig
    • OutlierDetectionRawConfig
    • EndpointMap
  • Moved out of the experimental namespace:
    • ServiceConfig
    • MethodConfig
    • LoadBalancingConfig (now a simple raw object type)
    • RetryPolicy
  • Removed:
    • getFirstUsableConfig
    • validateLoadBalancingConfig
    • OutlierDetectionLoadBalancingConfig
  • Modified:
    • LoadBalancer#updateAddressList: The first argument now has type Endpoint[] instead of SubchannelAddress[]
    • ResolverListener#onSuccessfulResolution: The first argument now has type Endpoint[] instead of SubchannelAddress[]
    • registerLoadBalancerType: The second argument, a LoadBalancerConstructor now takes a second argument options: ChannelOptions
    • ConfigSelector: Now accepts an additional argument channelId: number
    • QueuePicker: The constructor now accepts an additional optional argument childPicker: Picker, which the QueuePicker instance will delegate to if provided.

Configuration

📅 Schedule: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate-bot renovate-bot requested review from a team as code owners February 7, 2024 10:29
@product-auto-label product-auto-label bot added the size: xs Pull request size is extra small. label Feb 7, 2024
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Feb 7, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 7, 2024
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 7, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 7, 2024
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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 7, 2024
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 8, 2024
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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 8, 2024
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Feb 8, 2024
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 8, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 8, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 8, 2024
@gcf-merge-on-green gcf-merge-on-green bot merged commit ea84b7b into googleapis:main Feb 8, 2024
18 checks passed
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Feb 8, 2024
This was referenced Feb 8, 2024
@renovate-bot renovate-bot deleted the renovate/grpc-grpc-js-1.x branch March 12, 2024 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size: xs Pull request size is extra small.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants