Skip to content

Update duckdb_jdbc to 1.4.0.0#4042

Merged
xerial merged 1 commit intomainfrom
update/duckdb_jdbc-1.4.0.0
Sep 18, 2025
Merged

Update duckdb_jdbc to 1.4.0.0#4042
xerial merged 1 commit intomainfrom
update/duckdb_jdbc-1.4.0.0

Conversation

@xerial-bot
Copy link
Collaborator

About this PR

📦 Updates org.duckdb:duckdb_jdbc from 1.3.2.1 to 1.4.0.0

Usage

Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.duckdb", artifactId = "duckdb_jdbc" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.duckdb", artifactId = "duckdb_jdbc" }
}]
labels: library-update

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.

Summary of Changes

Hello @xerial-bot, 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 automates the update of the duckdb_jdbc library to its latest stable version, 1.4.0.0. This ensures the project benefits from the newest features, performance improvements, and bug fixes provided by the DuckDB JDBC driver.

Highlights

  • Dependency Update: The org.duckdb:duckdb_jdbc library has been updated from version 1.3.2.1 to 1.4.0.0.
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 updates the duckdb_jdbc dependency to version 1.4.0.0. While this is a straightforward version bump, I've provided a suggestion to improve the maintainability of the build.sbt file. The recommendation is to define the dependency version as a constant, which aligns with the existing coding style in the file for other dependencies and centralizes version management.

libraryDependencies ++= Seq(
"org.xerial" % "sqlite-jdbc" % SQLITE_JDBC_VERSION,
"org.duckdb" % "duckdb_jdbc" % "1.3.2.1",
"org.duckdb" % "duckdb_jdbc" % "1.4.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

For consistency with how other dependency versions are managed in this file (e.g., SQLITE_JDBC_VERSION), it is better to define this version as a val at the top of build.sbt. This improves maintainability by centralizing version management.

You can add the following at the top of the file:

val DUCKDB_JDBC_VERSION = "1.4.0.0"

Then, you can use this constant here.

        "org.duckdb"     % "duckdb_jdbc" % DUCKDB_JDBC_VERSION,

@xerial xerial merged commit 084a734 into main Sep 18, 2025
25 checks passed
@xerial xerial deleted the update/duckdb_jdbc-1.4.0.0 branch September 18, 2025 03:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants