Skip to content

Update HikariCP to 6.3.2 #3999

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

Merged
merged 1 commit into from
Aug 8, 2025
Merged

Update HikariCP to 6.3.2 #3999

merged 1 commit into from
Aug 8, 2025

Conversation

xerial-bot
Copy link
Collaborator

About this PR

📦 Updates com.zaxxer:HikariCP from 6.3.1 to 6.3.2

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 = "com.zaxxer", artifactId = "HikariCP" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.zaxxer", artifactId = "HikariCP" }
}]
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 performs a routine dependency update, specifically upgrading the HikariCP connection pool library to its latest patch version. This ensures the project benefits from any bug fixes or minor improvements in the updated release of HikariCP.

Highlights

  • Dependency Update: Upgraded the com.zaxxer:HikariCP library from version 6.3.1 to 6.3.2.
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 or fill out our survey to provide feedback.

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, generated by Scala Steward, updates the com.zaxxer:HikariCP dependency from version 6.3.1 to 6.3.2. The change itself is correct. My review includes a suggestion to improve maintainability by defining the dependency version as a constant, which would align with existing patterns in the build.sbt file and make future updates easier to manage.

@@ -726,7 +726,7 @@ lazy val jdbc =
"org.xerial" % "sqlite-jdbc" % SQLITE_JDBC_VERSION,
"org.duckdb" % "duckdb_jdbc" % "1.3.2.0",
"org.postgresql" % "postgresql" % "42.7.7",
"com.zaxxer" % "HikariCP" % "6.3.1",
"com.zaxxer" % "HikariCP" % "6.3.2",
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 better maintainability and consistency, consider defining this version as a val at the top of the file, similar to how SQLITE_JDBC_VERSION and SLF4J_VERSION are handled. This centralizes version management and improves readability.

For example:

// Near the top of the build file
val HIKARI_CP_VERSION = "6.3.2"

// In libraryDependencies
"com.zaxxer"     % "HikariCP"    % HIKARI_CP_VERSION,

@xerial xerial merged commit ef6a558 into main Aug 8, 2025
20 checks passed
@xerial xerial deleted the update/HikariCP-6.3.2 branch August 8, 2025 23:53
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