Skip to content

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

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.

Sign up for GitHub

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

Closed
lqiu96 wants to merge 1 commit into from
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dependencies.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ io.perfmark:perfmark-api,perfmark-api=0.27.0
# Note: This is the google opentelemetry exporter and not the general opentelemetry project
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

@gemini-code-assist gemini-code-assist bot Mar 16, 2026

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)

dev.cel:cel,dev.cel=0.11.1
com.google.crypto.tink:tink,com.google.crypto.tink=1.20.0
# The follow opentelemetry dependencies have a different version from the opentelemetry-bom
Expand Down
Loading