Skip to content

chore(deps): update upper bound dependencies file#4112

Merged
lqiu96 merged 1 commit intomainfrom
renovate/upper-bound-dependencies-file
Feb 18, 2026
Merged

chore(deps): update upper bound dependencies file#4112
lqiu96 merged 1 commit intomainfrom
renovate/upper-bound-dependencies-file

Conversation

@lqiu96
Copy link
Member

@lqiu96 lqiu96 commented Feb 18, 2026

This PR contains the following updates:

Package Update Change
com.google.auth:google-auth-library-bom minor 1.42.1 -> 1.43.0
com.google.errorprone:error_prone_annotations (source) minor 2.46.0 -> 2.47.0
com.google.protobuf:protobuf-java (source) patch 4.33.4 -> 4.33.5
io.grpc:grpc-bom minor 1.78.0 -> 1.79.0
io.opentelemetry:opentelemetry-bom minor 1.58.0 -> 1.59.0
org.apache.httpcomponents.core5:httpcore5 patch 5.4 -> 5.4.1

Release Notes

googleapis/google-auth-library-java (com.google.auth:google-auth-library-bom)

v1.43.0

Compare Source

Features
Bug Fixes
  • Deserialization checks valid class types for HttpTransportFactory (#​1882) (76ff74e)
google/error-prone (com.google.errorprone:error_prone_annotations)

v2.47.0: Error Prone 2.47.0

Compare Source

New checks:

Closed issues: #​1811, #​4168, #​5459, #​5460

Full changelog: google/error-prone@v2.46.0...v2.47.0

grpc/grpc-java (io.grpc:grpc-bom)

v1.79.0

Compare Source

API Changes

  • core: Delete the never-used io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (#​12580) (738782f). This is deeply internal and not accessible, so shouldn’t impact anything. However, Apache Arrow Java uses reflection to access private fields; GH-939: Remove reflection for gRPC buffers is swapping to gRPC’s public zero-copy APIs

  • opentelemetry: Add target attribute filter for metrics (#​12587). Introduce an optional Predicate targetAttributeFilter to control how grpc.target is recorded in OpenTelemetry client metrics. When a filter is provided, targets rejected by the predicate are normalized to "other" to reduce grpc.target metric cardinality, while accepted targets are recorded as-is. If no filter is set, existing behavior is preserved. This change adds a new Builder API on GrpcOpenTelemetry to allow applications to configure the filter. 

Behavior Changes

  • core: Convert AutoConfiguredLB to an actual LB (4bbf8ee). This is an internal refactoring, but it does improve how errors are handled for broken binaries. Previously, not being able to load pick_first would result in a channel panic. Now it is handled as a regular load balancing error

  • okhttp: Assert no pending streams before transport READY (#​12566) (ed6d175). No pending streams should exist when the transport transitions to READY. This PR adds an assertion to help verify this invariant.

Bug Fixes

  • core: PickFirstLB should not return a subchannel during CONNECTING (228fc8e). Pick-first in grpc-java has behaved this way since it was created, and it was of no consequence. However, now there are some load balancing policies (mainly RLS) that will do a pick() and hope the result to be reasonably accurate for metrics.

Improvements

  • core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b). Previously the error message contained “buffered_nanos” and “waiting_for_connection” for connection delays. However, we discovered the same strings were also used if waiting on CallCredentials. Now you’ll see details like “connecting_and_lb_delay”, “call_credentials_delay”, and “was_still_waiting”.

  • opentelemetry: Add Android API checking (a9f73f4). Previously we assumed OpenTelemetry support would not be used on Android. It did happen to be compatible with Android, but since OpenTelemetry does have some Android support, we now have a check that it remains compatible

  • core: Catch Errors when calling complex config parsing code (a535ed7). Error (and any other Throwable) is now caught and handled when parsing configuration (e.g., service config, xds). This will cause such failures to be handled gracefully instead of panicking the channel

  • core: Implement LoadBalancer.Helper.createOobChannel() with the internals of createResolvingOobChannel() (3915d02). This API is only expected to be relevant to the gRPC-LB lookaside load balancer, and is not believed to have behavior changes. Out-of-band channel had been implemented with its own stripped-down Channel without load balancing. Reimplementing using the resolving oob channel makes it a full-fledged channel and reduces the burden when integrating new features and allows us to have a ManagedChannelBuilder to use with efforts like gRFC A110: Child Channel Options.

  • xds: Implement the proactive connection logic in RingHashLoadBalancer as outlined in gRFC A61 (#​12596). Previously, the Java implementation only initialized child balancers when a ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel call. This PR adds the missing logic: when a child balancer reports TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first available IDLE child if no other children are currently connecting or ready.

This ensures a backup subchannel starts warming up immediately outside the RPC flow, reducing failover latency and improving overall resilience. This behavior was previously present but was inadvertently lost after #​10610.

  • api: Add RFC 3986 support to DnsNameResolverProvider (#​12602) (f65127c) Experimental RFC 3986 target URI parsing mode (disabled by default)

New Features

Dependencies 

  • protobuf: Upgrade Bazel protobuf to 33.1 (#​12553) (b61a8f4) and load java_proto_library from the protobuf repo (c7f3cdb)

  • protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and grpc-proto versions (#​12569)

  • Upgrade dependencies (#​12588) (6422092) Netty to 4.1.130, error-prone annotations to 2.45.0, google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 1.41.0, proto-google-common-protos to 2.63.2.

Thanks to

open-telemetry/opentelemetry-java (io.opentelemetry:opentelemetry-bom)

v1.59.0

Compare Source

API
  • Stabilize complex attributes
    (#​7973)
  • Limit init valid hex array to range that can be true
    (#​7809)
Extensions
  • Trace propagators: Deprecate OtTracePropagator
    (#​8020)
  • Trace propagators: Deprecate JaegerPropagator
    (#​8019)
SDK
  • Move io.opentelemetry.sdk.internal to io.opentelemetry.sdk.common.internal
    (#​8003)
  • Always return ExtendedOpenTelemetry when incubator is available
    (#​7991)
Traces
  • Fix memory leak in SdkSpan#spanEndingThread
    (#​7984)
Metrics
  • Rework and publish metric benchmarks
    (#​8000)
  • Update LongLastValueAggregator algo to avoid allocations
    (#​8017)
Testing
  • Fix OTel JUnit5 Extension cleanup when using Nested test classes
    (#​7999)
  • Add assertion support for Span hasException(null)
    (#​8033)
Exporters
  • DEPRECATION: opentelemetry-exporter-zipkin is now deprecated with the
    last release planned for 1.65.0 (August 2026)
    (#​7974)
  • Refactor http, grpc senders and promote to public API
    (#​7782)
Extensions
  • Jaeger remote sampler: Remove unused code
    (#​7970)
  • Incubator: Add AlwaysRecordSampler
    (#​7877)
Project tooling
  • Align generate release contributors
    (#​8023)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@product-auto-label product-auto-label bot added the size: s Pull request size is small. label Feb 18, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @lqiu96, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine update of several key Java dependencies to their latest stable versions. The updates encompass minor and patch releases for libraries such as Google Auth, Error Prone, gRPC, OpenTelemetry, Protobuf, and Apache HttpComponents. This ensures the project benefits from the latest features, bug fixes, performance improvements, and security enhancements provided by these upstream libraries, maintaining compatibility and stability within the ecosystem.

Highlights

  • Dependency Updates: Updated google-auth-library-bom from 1.42.1 to 1.43.0, introducing a bug fix for deserialization checks in HttpTransportFactory.
  • Error Prone Enhancements: Upgraded error_prone_annotations from 2.46.0 to 2.47.0, adding new checks like InterruptedInCatchBlock, RefactorSwitch, and UnnamedVariable.
  • gRPC Improvements: Updated grpc-bom from 1.78.0 to 1.79.0, bringing API changes, behavior improvements (e.g., better error handling for broken binaries), bug fixes, and new OpenTelemetry features for subchannel metrics.
  • OpenTelemetry Updates: Bumped opentelemetry-bom from 1.58.0 to 1.59.0, stabilizing complex attributes, deprecating OtTracePropagator and JaegerPropagator, and fixing a memory leak in SdkSpan.
  • Minor Dependency Bumps: Applied patch updates for protobuf-java (4.33.4 to 4.33.5) and httpcore5 (5.4 to 5.4.1).
Changelog
  • dependencies.txt
    • Updated io.grpc:grpc-bom from 1.78.0 to 1.79.0.
    • Updated com.google.auth:google-auth-library-bom from 1.42.1 to 1.43.0.
    • Updated com.google.protobuf:protobuf-java from 4.33.4 to 4.33.5.
    • Updated io.opentelemetry:opentelemetry-bom from 1.58.0 to 1.59.0.
    • Updated com.google.errorprone:error_prone_annotations from 2.46.0 to 2.47.0.
    • Updated org.apache.httpcomponents.core5:httpcore5 from 5.4 to 5.4.1.
Activity
  • This pull request was automatically generated by Renovate Bot to update project dependencies.
  • No human activity or reviews have been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

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

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, generated by Renovate, updates the versions of several dependencies in the dependencies.txt file, which tracks upper-bound versions for compatibility testing. The changes are all minor or patch updates. My review focuses on the consistency of these version bumps with the rest of the project. I've noted one potential inconsistency where a dependency version that was previously synchronized with the build configuration is now diverging. This might be unintentional and could be worth addressing to ensure the project uses the latest bug fixes from the new version.

io.grpc:grpc-bom,grpc=1.78.0
com.google.auth:google-auth-library-bom,google.auth=1.42.1
io.grpc:grpc-bom,grpc=1.79.0
com.google.auth:google-auth-library-bom,google.auth=1.43.0
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The version of com.google.auth:google-auth-library-bom is being updated to 1.43.0 in this upper-bound tracking file. However, the version used in the build, defined by the google.auth.version property in gapic-generator-java-pom-parent/pom.xml, remains at 1.42.1. While other dependencies in this file are also out of sync with the build, this particular dependency was aligned before this change. This divergence could be unintentional. Please consider updating google.auth.version in gapic-generator-java-pom-parent/pom.xml to 1.43.0 in this or a subsequent PR to maintain consistency and adopt the bug fixes from the new version.

@sonarqubecloud
Copy link

@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@lqiu96 lqiu96 merged commit ffb6b02 into main Feb 18, 2026
59 of 61 checks passed
@lqiu96 lqiu96 deleted the renovate/upper-bound-dependencies-file branch February 18, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: s Pull request size is small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments