fix(deps): update dependency com.zaxxer:hikaricp to v6.1.0

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.zaxxer:HikariCP	6.0.0 -> 6.1.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: maven/com.zaxxer/HikariCP@6.0.0

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	maven/log4j/log4j@1.2.16	CVE: GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x (CRITICAL) Affected versions: <= 2.0 Patched version: No patched versions	pom.xml sagalog-postgres/pom.xml	⚠︎
Critical CVE	maven/log4j/log4j@1.2.16	CVE: GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j (CRITICAL) Affected versions: <= 2.0 Patched version: No patched versions	pom.xml sagalog-postgres/pom.xml	⚠︎
Critical CVE	maven/log4j/log4j@1.2.16	CVE: GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j (CRITICAL) Affected versions: >= 1.2, <= 1.2.17 Patched version: No patched versions	pom.xml sagalog-postgres/pom.xml	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore maven/log4j/log4j@1.2.16