chore: update upper bound dependencies file

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
com.google.crypto.tink:tink	1.18.0 -> 1.19.0
com.google.errorprone:error_prone_annotations (source)	2.42.0 -> 2.43.0
dev.cel:cel	0.11.0 -> 0.11.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

tink-crypto/tink-java (com.google.crypto.tink:tink)

v1.19.0: Tink Java v1.19.0

Compare Source

Tink is a multi-language, cross-platform library that provides simple and misuse-proof APIs for common cryptographic tasks.

This is Tink Java 1.19

The complete list of changes since 1.18.0 can be found here.

Build changes

• For Bazel builds, we now use Bazel 7.6.1. in our tests.
• For Bazel builds, Tink now supports bzlmod.
• Tink no longer supports Java 8. The minimum version starting from 1.19.0 is Java 11.

Dependencies

• Protobuf 4.28.2 was upgraded to Protobuf 4.32.1. (Note: we plan to shade protobuf in the next minor version of Tink which should resolve compatibility issues)

Obscure behaviour changes

• Tink will reject custom key types where the Type-Url has non-ASCII characters.

• Tink may serialize keysets slightly differently in certain cases. For
  example, in the serialization of a ECDSA keyset, the points might be padded
  differently than before. Users should not depend on the exact format of
  Tink's serialization.

• Use Conscrypt's AES-CMAC implementation when available and when the input is larger than 64 byte. This may improves the performance of AES-CMAC, AES-SIV and AES-EAX for large inputs.

• Removed usage of thread-local Ciphers for ChaCha20Poly1305.

Added APIs

• Added public JwtEcdsaParameters.Algorithm.getEcParameterSpec method.

• The AES-SIV implementation in subtle now accepts multiple associated datas.

Future work

To see what we're working towards, check our project roadmap.

Getting started

To get started using Tink, see the setup guide.

Maven:

<dependency>
    <groupId>com.google.crypto.tink</groupId>
    <artifactId>tink</artifactId>
    <version>1.19.0</version>
</dependency>

Gradle:

dependencies {
  implementation 'com.google.crypto.tink:tink-android:1.19.0'
}

Bazel:

Using bzlmod

bazel_dep(name = "tink_java", version = "1.19.0")

git_override(
    module_name = "tink_java",
    remote = "https://github.com/tink-crypto/tink-java",
    tag = "v1.19.0",
)

Using WORKSPACE

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "4.5"
RULES_JVM_EXTERNAL_SHA ="b17d7388feb9bfa7f2fa09031b32707df529f26c91ab9e5d909eb1676badd9a6"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazelbuild/rules_jvm_external/archive/refs/tags/%s.zip" % RULES_JVM_EXTERNAL_TAG,
)

load("@​rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@​rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

load("@​rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "com.google.crypto.tink:tink:NEXT_VERSION",
        # ... other dependencies ...
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
)

Alternatively, one can build Tink from source, and include it with
http_archive:

http_archive(
    name = "com_github_tink_crypto_tink_java",
    urls = ["https://github.com/tink-crypto/tink-java/archive/refs/tags/NEXT_VERSION.zip"],
    strip_prefix = "tink-java-NEXT_VERSION",
    sha256 = ...
)

load("@​tink_java//:tink_java_deps.bzl", "TINK_MAVEN_ARTIFACTS", "tink_java_deps")

tink_java_deps()

load("@​tink_java//:tink_java_deps_init.bzl", "tink_java_deps_init")

tink_java_deps_init()

# ...

maven_install(
    artifacts = TINK_MAVEN_ARTIFACTS + # ... other dependencies ...
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
)

google/error-prone (com.google.errorprone:error_prone_annotations)

v2.43.0: Error Prone 2.43.0

Changes:

• -XepPatchChecks now skips disabled checks (#​4943)
• AndroidJdkLibsChecker has been removed, the recommended replacement for Android code is Android Lint's NewApi check

New checks:

• NullNeedsCastForVarargs: Detect calls that incorrectly passes a null array instead of a null element.
• RedundantNullCheck: detect checks on expressions that are non-null.

Closed issues: #​4943, #​5102, #​5107, #​5121, #​5158, #​5217, #​5239

Full changelog: google/error-prone@v2.42.0...v2.43.0

google/cel-java (dev.cel:cel)

v0.11.1

Compare Source

Significant changes

• CEL-Java evaluates the following expressions to their proto equivalent form:

timestamp(100) -> google.protobuf.Timestamp
duration("1h") -> google.protobuf.Duration

Starting with this release, the runtime can evaluate these literals to the following Java native type equivalents:

timestamp(100) -> java.time.Instant
duration("1h") -> java.time.Duration

This new behavior is not yet enabled by default. Call CelOptions.Builder.evaluateCanonicalTypesToNativeValues(true) to explicitly enable it.

• Previously only identifiers containing a period were allowed to be aliased. This constraint has been removed, so the following aliasing is now allowed:

CelContainer.newBuilder().addAlias("short", "really_long_package_name").build();

What's Changed

Features

• Evaluate CEL's timestamp and duration types to their native equivalent values in #​790
• Relax constraint for fully qualifying a package name when aliasing in #​837

Optimizations

• Enhance CSE to handle two variable comprehensions in #​808
• Override environment's expected result type during constant folding in #​815
• Allow constant folding to fold equals operator in #​822
• Enhance ConstantFoldingOptimizer to fold arithmetics involving timestamps and durations in #​825

Safety

• Add comprehension nesting validator. in #​829

Bug fixes

• Fixed negative zero comparison. "0.0 == -0.0" now evaluates to true
• Fixed FileDescriptorSetConverter to always reference WellKnownTypes descriptors from generated ones in #​833
• Fixed bytes(string) standard function to respect evaluateCanonicalTypesToNativeValues flag in #​828

Testing infra

• Setup of the coverage index. in #​811

Miscellaneous

• Renaming the CelComprehensionsExtensions docs to align more closely with lib implementation in #​807
• Remove capability to serially increment mangled variable indices in #​806
• Add an overload for CelMutableExpr.ofComprehension. in #​812
• Fix Typo: "descedent" to "descendent". in #​827
• Include comprehensions in CelEnvironment in #​838
• Update evaluateCanonicalTypesToNativeValues documentation and fix tests in #​840

Full Changelog: google/cel-java@v0.11.0...v0.11.1

---

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 was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! 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 focuses on maintaining the project's dependency hygiene by updating the tink cryptographic library and the cel Common Expression Language library to their latest minor versions. These updates bring a range of improvements, from security enhancements and API additions in tink to new features, performance optimizations, and bug fixes in cel. The changes ensure the project benefits from the most current capabilities and stability offered by these critical third-party components.

Highlights

• Dependency Updates: The pull request updates two key dependencies: com.google.crypto.tink:tink from version 1.18.0 to 1.19.0, and dev.cel:cel from version 0.11.0 to 0.11.1.
• Tink Library Enhancements: The tink update (v1.19.0) raises the minimum required Java version to 11, upgrades Protobuf to 4.32.1, and includes various build system improvements (Bazel 7.6.1, bzlmod support). It also introduces new APIs like JwtEcdsaParameters.Algorithm.getEcParameterSpec and allows AES-SIV to accept multiple associated datas.
• CEL Library Features and Optimizations: The cel update (v0.11.1) introduces an opt-in feature to evaluate CEL's timestamp and duration types to native Java Instant and Duration equivalents. It also relaxes constraints for aliasing package names, and includes several optimizations for Common Subexpression Elimination (CSE) and constant folding, along with bug fixes.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates two dependencies, dev.cel:cel and com.google.crypto.tink:tink. While the update for dev.cel:cel appears to be safe, the update for com.google.crypto.tink:tink to version 1.19.0 introduces a critical breaking change. This new version of Tink requires Java 11, but the project is currently configured for Java 8. This incompatibility will likely cause build failures and must be addressed before merging.

[gemini-code-assist]

The update of com.google.crypto.tink:tink to version 1.19.0 introduces a breaking change. According to the release notes, this version requires Java 11, but this project is configured to use Java 8 (as specified by <maven.compiler.release>8</maven.compiler.release> in gapic-generator-java-pom-parent/pom.xml). This will cause build failures. It's recommended to revert this change until the project is upgraded to Java 11.

com.google.crypto.tink:tink,com.google.crypto.tink=1.18.0