Skip to content

Update duckdb_jdbc to 1.3.2.1#4020

Merged
xerial merged 1 commit intomainfrom
update/duckdb_jdbc-1.3.2.1
Aug 29, 2025
Merged

Update duckdb_jdbc to 1.3.2.1#4020
xerial merged 1 commit intomainfrom
update/duckdb_jdbc-1.3.2.1

Conversation

@xerial-bot
Copy link
Copy Markdown
Collaborator

About this PR

📦 Updates org.duckdb:duckdb_jdbc from 1.3.2.0 to 1.3.2.1

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
Copy Markdown
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 updates the duckdb_jdbc library to its latest patch version, 1.3.2.1, ensuring the project benefits from the most recent bug fixes and minor improvements. This is a routine dependency update managed by Scala Steward.

Highlights

  • Dependency Update: The org.duckdb:duckdb_jdbc dependency has been upgraded from version 1.3.2.0 to 1.3.2.1. This is a patch version update, typically indicating bug fixes or minor enhancements.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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
Copy Markdown
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 org.duckdb:duckdb_jdbc dependency from 1.3.2.0 to 1.3.2.1. This is a patch version bump and appears to be a safe, routine update. I've included one suggestion to improve the maintainability of build.sbt by extracting the version string into a constant, which aligns with the existing coding style for other dependencies in the file.

Comment thread build.sbt
libraryDependencies ++= Seq(
"org.xerial" % "sqlite-jdbc" % SQLITE_JDBC_VERSION,
"org.duckdb" % "duckdb_jdbc" % "1.3.2.0",
"org.duckdb" % "duckdb_jdbc" % "1.3.2.1",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability and consistency, consider extracting the hardcoded version string into a val at the top of the file, similar to how other dependencies like SQLITE_JDBC_VERSION are handled.

This would involve:

  1. Defining a new val at the top of build.sbt, for example: val DUCKDB_JDBC_VERSION = "1.3.2.1".
  2. Using this val here instead of the string literal.

This practice improves code clarity and simplifies future dependency updates.

@xerial xerial merged commit 1cec96d into main Aug 29, 2025
25 checks passed
@xerial xerial deleted the update/duckdb_jdbc-1.3.2.1 branch August 29, 2025 00:13
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