Skip to content

chore(deps): update dependency org.apache.arrow:arrow-memory-core to v19#4147

Closed
lqiu96 wants to merge 1 commit intomainfrom
renovate/major-upper-bound-dependencies-file
Closed

chore(deps): update dependency org.apache.arrow:arrow-memory-core to v19#4147
lqiu96 wants to merge 1 commit intomainfrom
renovate/major-upper-bound-dependencies-file

Conversation

@lqiu96
Copy link
Member

@lqiu96 lqiu96 commented Mar 16, 2026

This PR contains the following updates:

Package Update Change
org.apache.arrow:arrow-memory-core major 18.3.0 -> 19.0.0

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: xs Pull request size is extra small. label Mar 16, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 dependency update, specifically upgrading the Apache Arrow memory core library to its latest major version. This ensures the project benefits from the newest features, performance improvements, and bug fixes provided by the updated library, maintaining compatibility and leveraging modern capabilities.

Highlights

  • Dependency Update: The org.apache.arrow:arrow-memory-core dependency has been updated from version 18.3.0 to 19.0.0.
Changelog
  • dependencies.txt
    • Updated org.apache.arrow:arrow-memory-core from 18.3.0 to 19.0.0.
Activity
  • This pull request was automatically generated by Renovate Bot.
  • Automerge is currently disabled, requiring manual merging after review.
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

The pull request updates the org.apache.arrow:arrow-memory-core dependency to version 19.0.0 in the dependencies.txt file. This change reflects a major version update for this external dependency. It's important to consider the implications of major version bumps, especially in light of the project's dependency management guidelines.

com.google.cloud.opentelemetry:exporter-metrics,google.cloud.opentelemetry=0.36.0
com.google.flogger:flogger,flogger=0.9
org.apache.arrow:arrow-memory-core,arrow=18.3.0
org.apache.arrow:arrow-memory-core,arrow=19.0.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

This pull request updates the arrow-memory-core dependency to a new major version (19.0.0) in dependencies.txt. The repository's dependency management guidelines (Repository Style Guide, line 137) advise against bumping external dependency versions unless there is a known CVE or critical bug fix. While dependencies.txt tracks the 'currently known upper bound' for compatibility testing, a major version update often introduces breaking changes. It would be beneficial to clarify the justification for tracking this major version at this time, especially if there's no immediate plan to integrate it into the pom.xml files, to ensure alignment with the project's dependency management strategy.

References
  1. Try not to bump any external dependency version unless there is a known CVE (security or vulnerability issue) or a critical bug fix. (link)

@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 closed this Mar 17, 2026
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.

2 participants