Skip to content

Update postgresql to 42.7.7 #3966

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

Jump to bottom
Merged
merged 1 commit into from
Jul 12, 2025
Merged

Update postgresql to 42.7.7 #3966

merged 1 commit into from
Jul 12, 2025

Conversation

xerial-bot
Copy link
Collaborator

About this PR

📦 Updates org.postgresql:postgresql from 42.7.6 to 42.7.7

📜 Changelog

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.postgresql", artifactId = "postgresql" } ]

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

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

gemini-code-assist[bot]
gemini-code-assist bot reviewed Jun 11, 2025
View reviewed changes
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 is an automated dependency update, bumping the version of the PostgreSQL JDBC driver used in the project. It also includes a minor formatting adjustment in the build file.

Highlights

  • Dependency Update: Updates the org.postgresql:postgresql dependency from version 42.7.6 to 42.7.7 in the jdbc project definition.
  • Build File Formatting: Includes a minor indentation change for an exclude rule in the fluentd project definition within build.sbt. This appears to be a formatting change unrelated to the dependency update itself.
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 is currently in preview and 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 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 configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Jun 11, 2025
View reviewed changes
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 PostgreSQL JDBC driver to version 42.7.7. There's also an indentation change to an exclude rule in build.sbt. The exclude rule appears to be incorrectly formulated and positioned, likely rendering it ineffective. It's recommended to review the necessity and implementation of this exclusion rule.

build.sbt Outdated
@@ -962,7 +962,7 @@ lazy val fluentd =
"org.komamitsu" % "fluency-fluentd" % FLUENCY_VERSION,
"org.komamitsu" % "fluency-treasuredata" % FLUENCY_VERSION
// td-client-java -> json-simple happened to include junit 4.10 [CVE-2020-15250]
exclude ("junit", "junit"),
exclude ("junit", "junit"),
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The indentation of this exclude line has increased from 8 spaces to 10 spaces. For consistency with other elements in the Seq (e.g., lines 962-963 and 967-968, which are indented by 8 spaces), this line should also be indented by 8 spaces.

More importantly, an ExclusionRule like exclude("junit", "junit") placed directly as an item in the libraryDependencies sequence is unlikely to have the desired effect of excluding a transitive dependency.
To exclude junit from a specific dependency (e.g., fluency-treasuredata), the syntax would typically be:

"org.komamitsu" % "fluency-treasuredata" % FLUENCY_VERSION exclude("junit", "junit")

Or, for a project-level exclusion (if this fluentd project is defined with .settings(...)):

excludeDependencies += ExclusionRule("junit", "junit")

Please verify:

  1. If this exclusion is still necessary. The comment on line 964 refers to a CVE related to junit as a transitive dependency via td-client-java -> json-simple. A quick check suggests junit might not be a transitive dependency of org.komamitsu:fluency-treasuredata:2.7.3 through this path with current versions.
  2. If the exclusion is necessary, it should be applied using the correct sbt syntax to ensure it's effective.

The current form is likely non-functional and could lead to confusion or a false sense of security regarding the CVE mentioned.

        exclude ("junit", "junit"),

@xerial-bot xerial-bot force-pushed the update/postgresql-42.7.7 branch from 7dad25a to 7df77ce Compare July 9, 2025 20:06
@xerial-bot xerial-bot force-pushed the update/postgresql-42.7.7 branch from 7df77ce to 5dd09b8 Compare July 12, 2025 20:06
@xerial xerial enabled auto-merge (squash) July 12, 2025 20:12
@xerial xerial merged commit ce75259 into main Jul 12, 2025
17 checks passed
@xerial xerial deleted the update/postgresql-42.7.7 branch July 12, 2025 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
library-update
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@xerial-bot @xerial