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

Update gradle locks (Automated) #267

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hypertrace-ci-app[bot]
Copy link
Contributor

@hypertrace-ci-app hypertrace-ci-app bot commented Feb 14, 2025

User description

Autogenerated gradle lock updates


CodeAnt-AI Description

  • Updated multiple dependencies across gradle.lockfile files to newer versions, ensuring compatibility and leveraging improvements.
  • Significant updates include grpc from 1.60.0 to 1.68.3, netty from 4.1.108.Final to 4.1.118.Final, and hypertrace-bom from 0.3.23 to 0.3.45.
  • These updates are part of routine maintenance to keep the project dependencies up to date.

Changes walkthrough

Relevant files
Dependencies
gradle.lockfile
Update dependencies in gradle.lockfile for hypertrace-graphql-service

hypertrace-graphql-service/gradle.lockfile

  • Updated proto-google-common-protos from version 2.22.0 to 2.41.0.
  • Updated gson from version 2.10.1 to 2.11.0.
  • Updated grpc dependencies from version 1.60.0 to 1.68.3.
  • Updated netty dependencies from version 4.1.108.Final to
    4.1.118.Final.
  • +74/-70 
    gradle.lockfile
    Update dependencies in gradle.lockfile for
    hypertrace-graphql-service-config

    hypertrace-graphql-service-config/gradle.lockfile

  • Updated graphql-java from version 19.6 to 19.11.
  • Updated grpc-bom from version 1.60.0 to 1.68.3.
  • Added netty-bom version 4.1.118.Final.
  • Updated hypertrace-bom from version 0.3.23 to 0.3.45.
  • +6/-4     
    💡 Usage Guide

    Checking Your Pull Request

    Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

    Talking to CodeAnt AI

    Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

    @codeant-ai ask: Your question here
    

    This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

    Retrigger review

    Ask CodeAnt AI to review the PR again, by typing:

    @codeant-ai: review
    

    Check Your Repository Health

    To analyze the health of your code repository, visit our dashboard at app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

    @hypertrace-ci-app hypertrace-ci-app bot requested a review from a team as a code owner February 14, 2025 12:50
    @codeant-ai codeant-ai bot added the size:L This PR changes 100-499 lines, ignoring generated files label Feb 14, 2025
    Copy link

    codeant-ai bot commented Feb 14, 2025

    Pull Request Feedback 🔍

    🔒 No security issues identified
    ⚡ Recommended areas for review

    Dependency Update
    The PR updates multiple dependencies to newer versions. Ensure that these updates do not introduce any compatibility issues or require additional changes in the codebase.

    Dependency Update
    The PR updates several dependencies, including grpc and netty. Verify that these updates are compatible with the existing code and do not introduce any breaking changes.

    Comment on lines +22 to +23
    com.google.j2objc:j2objc-annotations:2.8=runtimeClasspath,testRuntimeClasspath
    com.google.j2objc:j2objc-annotations:3.0.0=compileClasspath,testCompileClasspath
    Copy link

    Choose a reason for hiding this comment

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

    Suggestion: Review the necessity of including both j2objc-annotations:2.8 and j2objc-annotations:3.0.0 as they might conflict or be redundant. [maintainability]

    Suggested change
    com.google.j2objc:j2objc-annotations:2.8=runtimeClasspath,testRuntimeClasspath
    com.google.j2objc:j2objc-annotations:3.0.0=compileClasspath,testCompileClasspath
    com.google.j2objc:j2objc-annotations:3.0.0=compileClasspath,testCompileClasspath

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    size:L This PR changes 100-499 lines, ignoring generated files
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    1 participant