build(deps-dev): Bump org.postgresql:postgresql from 42.7.9 to 42.7.12 in the maven group across 1 directory #14

Open
dependabot[bot] wants to merge 1 commits from dependabot/maven/maven-55f3996f77 into develop
pull from: dependabot/maven/maven-55f3996f77
dependabot[bot] commented 2026-10-15 01:46:18 +00:00 (Migrated from github.com)

Bumps the maven group with 1 update in the / directory: org.postgresql:postgresql.

Updates org.postgresql:postgresql from 42.7.9 to 42.7.12

Release notes

Sourced from org.postgresql:postgresql's releases.

v42.7.12: security

Silent channel-binding authentication downgrade (CVE-2026-54291)

channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms.

Two issues combine in releases 42.7.4 through 42.7.11:

The bundled com.ongres.scram:scram-client (3.1 or 3.2) returns an empty byte array instead of failing when it cannot derive the binding hash for such a certificate. This is the library issue tracked as GHSA-p9jg-fcr6-3mhf.

pgJDBC does not enforce channelBinding=require where it matters. ScramAuthenticator checks only that the server advertised a -PLUS mechanism; it neither rejects the empty binding nor checks that the negotiated mechanism uses channel binding. The connection therefore downgrades silently.

Only connections that set channelBinding=require are affected. Under the default prefer policy, and under allow or disable, falling back to plain SCRAM is the documented behaviour.

Releases before 42.7.4 are unaffected, because they do not support channel binding.

v42.7.11

Security

  • fix: Limit SCRAM PBKDF2 iterations accepted from the server. pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins. See the Security Advisory for more detail. The following CVE-2026-42198 has been issued.

Changes

🐛 Bug Fixes

  • fix: ensure extended protocol messages end with Sync message @​vlsi (#3728)
  • fix: enable cursor-based fetching in extended protocol when transaction started via SQL command @​vlsi (#3996)
  • fix: retry with SSL on IOException when sslMode=ALLOW @​vlsi (#3973)
  • fix: allow fallback to non-SSL connection when sslMode=prefer and sslResponseTimeout kicks in @​vlsi (#3968)
  • fix: catch SecurityException from setContextClassLoader on ForkJoinPool workers @​vlsi (#3962)
  • fix: use compareTo for LogSequenceNumber comparison @​vlsi (#3961)

... (truncated)

Changelog

Sourced from org.postgresql:postgresql's changelog.

[42.7.12] (2026-06-29)

Security

  • fix: Enforce SCRAM channel-binding policy and prevent silent downgrade. Under channelBinding=require, the driver silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it) when the server presented a certificate whose signature algorithm has no tls-server-end-point channel-binding hash (e.g. Ed25519, Ed448, or post-quantum algorithms). An attacker who can intercept the TLS connection could exploit this to strip channel-binding protection. The fix enforces channel binding in the driver's own code: it now fails the connection when no binding data can be extracted, and verifies the negotiated mechanism uses channel binding (-PLUS) when require is set. Only connections that set channelBinding=require are affected. The default prefer policy and releases before 42.7.4 (which introduced channel-binding support) are unaffected. See the Security Advisory for more detail. The following CVE-2026-54291 has been issued.

[42.7.11] (2026-04-28)

Security

  • fix: Limit SCRAM PBKDF2 iterations accepted from the server. pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins. See the Security Advisory for more detail. The following CVE-2026-42198 has been issued.

Added

Changed

Fixed

[42.7.10] (2026-02-11)

Changed

Fixed

... (truncated)

Commits
  • 77df98e Merge commit from fork
  • 68c53a4 chore: bump version to 42.7.12
  • 78e261f fix: Add sources and javadocs to shaded published lib generation
  • 1e09fa0 update Changelog and website for release of 42.7.11 (#4042)
  • d479fa5 Fix scram fix location in changelog and update published artifact developer l...
  • b04fc46 docs: Add scram max iters fix to changelog
  • cf54822 test: Disable scram test on older version without scram_iterations GUC
  • 7dbcc79 test: Add SCRAM max iteration tests
  • c9d41d1 fix: Limit SCRAM PBKDF2 iterations accepted from the server
  • a340cb2 style: replace @​exception with @​throws in getBoolean javadoc
  • Additional commits viewable in compare view

Bumps the maven group with 1 update in the / directory: [org.postgresql:postgresql](https://github.com/pgjdbc/pgjdbc). Updates `org.postgresql:postgresql` from 42.7.9 to 42.7.12 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pgjdbc/pgjdbc/releases">org.postgresql:postgresql's releases</a>.</em></p> <blockquote> <h2>v42.7.12: security</h2> <h3>Silent channel-binding authentication downgrade (CVE-2026-54291)</h3> <p><code>channelBinding=require</code> connections can be silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms.</p> <p>Two issues combine in releases 42.7.4 through 42.7.11:</p> <p>The bundled <code>com.ongres.scram:scram-client</code> (3.1 or 3.2) returns an empty byte array instead of failing when it cannot derive the binding hash for such a certificate. This is the library issue tracked as <a href="https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf">GHSA-p9jg-fcr6-3mhf</a>.</p> <p>pgJDBC does not enforce channelBinding=require where it matters. ScramAuthenticator checks only that the server advertised a -PLUS mechanism; it neither rejects the empty binding nor checks that the negotiated mechanism uses channel binding. The connection therefore downgrades silently.</p> <p>Only connections that set channelBinding=require are affected. Under the default prefer policy, and under allow or disable, falling back to plain SCRAM is the documented behaviour.</p> <p>Releases before 42.7.4 are unaffected, because they do not support channel binding.</p> <h2>v42.7.11</h2> <h2>Security</h2> <ul> <li>fix: Limit SCRAM PBKDF2 iterations accepted from the server. pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins. See the <a href="https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-98qh-xjc8-98pq">Security Advisory</a> for more detail. The following <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-42198">CVE-2026-42198</a> has been issued.</li> </ul> <h2>Changes</h2> <ul> <li>fix: Add sources and javadocs to shaded published lib generation <a href="https://github.com/sehrope"><code>@​sehrope</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4043">#4043</a>)</li> <li>update Changelog and website for release of 42.7.11 <a href="https://github.com/davecramer"><code>@​davecramer</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4042">#4042</a>)</li> <li>Fix scram fix location in changelog and update published artifact developer list <a href="https://github.com/sehrope"><code>@​sehrope</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4041">#4041</a>)</li> <li>Restrict test with scram_iterations to v16+ and release notes <a href="https://github.com/sehrope"><code>@​sehrope</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4040">#4040</a>)</li> <li>chore(deps): update ubuntu:24.04 docker digest to 84e77de <a href="https://github.com/renovate-bot"><code>@​renovate-bot</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4017">#4017</a>)</li> <li>test: add tests for QueryExecutor#getTransactionState <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4006">#4006</a>)</li> <li>chore(deps): update actions/create-github-app-token action to v2.2.2 <a href="https://github.com/renovate-bot"><code>@​renovate-bot</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3983">#3983</a>)</li> <li>fix: fix flaky CopyBothResponseTest by using WAL flush LSN <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3979">#3979</a>)</li> <li>fix: fix flaky replication restart tests by waiting for confirmed_flush_lsn <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3975">#3975</a>)</li> <li>test: fix flaky LogicalReplicationStatusTest by polling pg_stat_replication <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3974">#3974</a>)</li> <li>chore: replace Appveyor with ikalnytskyi/action-setup-postgres <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3966">#3966</a>)</li> <li>test: move test table creation from <a href="https://github.com/BeforeEach"><code>@​BeforeEach</code></a> to <a href="https://github.com/BeforeAll"><code>@​BeforeAll</code></a> <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3967">#3967</a>)</li> <li>Return jsonb as PGObject fixes Issue <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3926">#3926</a> <a href="https://github.com/davecramer"><code>@​davecramer</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3956">#3956</a>)</li> <li>Update docker scripts <a href="https://github.com/davecramer"><code>@​davecramer</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3958">#3958</a>)</li> <li>implement require_auth, this is pretty much how libpq does this. <a href="https://github.com/davecramer"><code>@​davecramer</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3895">#3895</a>)</li> <li>docs: add SCRAM authentication test setup section to TESTING.md <a href="https://github.com/emmaeng700"><code>@​emmaeng700</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3945">#3945</a>)</li> <li>Add RequireServerVersion annotation for tests <a href="https://github.com/sehrope"><code>@​sehrope</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3939">#3939</a>)</li> </ul> <h2>🐛 Bug Fixes</h2> <ul> <li>fix: ensure extended protocol messages end with Sync message <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3728">#3728</a>)</li> <li>fix: enable cursor-based fetching in extended protocol when transaction started via SQL command <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3996">#3996</a>)</li> <li>fix: retry with SSL on IOException when sslMode=ALLOW <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3973">#3973</a>)</li> <li>fix: allow fallback to non-SSL connection when sslMode=prefer and sslResponseTimeout kicks in <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3968">#3968</a>)</li> <li>fix: catch SecurityException from setContextClassLoader on ForkJoinPool workers <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3962">#3962</a>)</li> <li>fix: use compareTo for LogSequenceNumber comparison <a href="https://github.com/vlsi"><code>@​vlsi</code></a> (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3961">#3961</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md">org.postgresql:postgresql's changelog</a>.</em></p> <blockquote> <h2>[42.7.12] (2026-06-29)</h2> <h3>Security</h3> <ul> <li>fix: Enforce SCRAM channel-binding policy and prevent silent downgrade. Under <code>channelBinding=require</code>, the driver silently downgraded from <code>SCRAM-SHA-256-PLUS</code> (with channel binding) to plain <code>SCRAM-SHA-256</code> (without it) when the server presented a certificate whose signature algorithm has no <code>tls-server-end-point</code> channel-binding hash (e.g. Ed25519, Ed448, or post-quantum algorithms). An attacker who can intercept the TLS connection could exploit this to strip channel-binding protection. The fix enforces channel binding in the driver's own code: it now fails the connection when no binding data can be extracted, and verifies the negotiated mechanism uses channel binding (<code>-PLUS</code>) when <code>require</code> is set. Only connections that set <code>channelBinding=require</code> are affected. The default <code>prefer</code> policy and releases before 42.7.4 (which introduced channel-binding support) are unaffected. See the <a href="https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-j92g-9f8w-j867">Security Advisory</a> for more detail. The following <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54291">CVE-2026-54291</a> has been issued.</li> </ul> <h2>[42.7.11] (2026-04-28)</h2> <h3>Security</h3> <ul> <li>fix: Limit SCRAM PBKDF2 iterations accepted from the server. pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins. See the <a href="https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-98qh-xjc8-98pq">Security Advisory</a> for more detail. The following <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-42198">CVE-2026-42198</a> has been issued.</li> </ul> <h3>Added</h3> <ul> <li>feat: implement require_auth connection property, aligning with libpq behavior [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3895">#3895</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3895">pgjdbc/pgjdbc#3895</a>)</li> </ul> <h3>Changed</h3> <ul> <li>chore: replace Appveyor CI with ikalnytskyi/action-setup-postgres [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3966">#3966</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3966">pgjdbc/pgjdbc#3966</a>)</li> <li>chore: upgrade Gradle to v9 [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3978">#3978</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3978">pgjdbc/pgjdbc#3978</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>fix: ensure extended protocol messages end with Sync message [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3728">#3728</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3728">pgjdbc/pgjdbc#3728</a>)</li> <li>fix: enable cursor-based fetching in extended protocol when transaction started via SQL command [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3996">#3996</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3996">pgjdbc/pgjdbc#3996</a>)</li> <li>fix: retry with SSL on IOException when sslMode=ALLOW [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3973">#3973</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3973">pgjdbc/pgjdbc#3973</a>)</li> <li>fix: make sure the driver honours connectTimeout when retrying the connection [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3968">#3968</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3968">pgjdbc/pgjdbc#3968</a>)</li> <li>fix: allow fallback to non-SSL connection when sslMode=prefer and sslResponseTimeout kicks in [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3968">#3968</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3968">pgjdbc/pgjdbc#3968</a>)</li> <li>fix: catch SecurityException from setContextClassLoader on ForkJoinPool workers [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3962">#3962</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3962">pgjdbc/pgjdbc#3962</a>)</li> <li>fix: use compareTo for LogSequenceNumber comparison to handle unsigned values correctly [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3961">#3961</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3961">pgjdbc/pgjdbc#3961</a>)</li> <li>fix: release COPY lock on IOException to prevent connection hang [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3957">#3957</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3957">pgjdbc/pgjdbc#3957</a>)</li> <li>fix: return jsonb as PGObject instead of String [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3956">#3956</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3956">pgjdbc/pgjdbc#3956</a>)</li> <li>fix: align SSL key file permission check with libpq [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3952">#3952</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3952">pgjdbc/pgjdbc#3952</a>)</li> <li>fix: guard connection closed flag with a reentrant lock to protect against concurrent close [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3905">#3905</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3905">pgjdbc/pgjdbc#3905</a>)</li> </ul> <h2>[42.7.10] (2026-02-11)</h2> <h3>Changed</h3> <ul> <li>chore: Migrate to Shadow 9 <a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3931">PR 3931</a></li> <li>style: fix empty line before javadoc for checkstyle compliance [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3925">#3925</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3925">pgjdbc/pgjdbc#3925</a>)</li> <li>style: fix lambda argument indentation for checkstyle compliance [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3922">#3922</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3922">pgjdbc/pgjdbc#3922</a>)</li> <li>test: add autosave=always|never|conservative and cleanupSavepoints=true|false to the randomized CI jobs [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3917">#3917</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3917">pgjdbc/pgjdbc#3917</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>fix: non-standard strings failing test for version 19 [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3934">#3934</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3934">pgjdbc/pgjdbc#3934</a>)</li> <li>fix: small issues in ConnectionFactoryImpl [PR <a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/3929">#3929</a>](<a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3929">pgjdbc/pgjdbc#3929</a>)</li> <li>fix: process pending responses before fastpath to avoid protocol errors <a href="https://redirect.github.com/pgjdbc/pgjdbc/pull/3913">PR # 3913</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/77df98e4e66c12936ded3478a0954f6f580bad99"><code>77df98e</code></a> Merge commit from fork</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/68c53a435291fea8be40eb1d9c550311743d326d"><code>68c53a4</code></a> chore: bump version to 42.7.12</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/78e261ff2a7f16a37bdceb2204f67e484387da2f"><code>78e261f</code></a> fix: Add sources and javadocs to shaded published lib generation</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/1e09fa0496377296c9e2ef3bfd2b409945fba17a"><code>1e09fa0</code></a> update Changelog and website for release of 42.7.11 (<a href="https://redirect.github.com/pgjdbc/pgjdbc/issues/4042">#4042</a>)</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/d479fa5b8c8c915a441ce1f2448f69f23dd0b66c"><code>d479fa5</code></a> Fix scram fix location in changelog and update published artifact developer l...</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/b04fc46af6c207bc7ce9e788fea8c43d18b73d0f"><code>b04fc46</code></a> docs: Add scram max iters fix to changelog</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/cf548225b4078db954765339720ffdf3bc94e5a6"><code>cf54822</code></a> test: Disable scram test on older version without scram_iterations GUC</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/7dbcc79b2b4adf7b71458c9434d2c43cec7713b9"><code>7dbcc79</code></a> test: Add SCRAM max iteration tests</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/c9d41d1332a7426fcef19ff89f2e6b1116429143"><code>c9d41d1</code></a> fix: Limit SCRAM PBKDF2 iterations accepted from the server</li> <li><a href="https://github.com/pgjdbc/pgjdbc/commit/a340cb2b0ae24c0d98ad9dec569200ebb704d6aa"><code>a340cb2</code></a> style: replace <a href="https://github.com/exception"><code>@​exception</code></a> with <a href="https://github.com/throws"><code>@​throws</code></a> in getBoolean javadoc</li> <li>Additional commits viewable in <a href="https://github.com/pgjdbc/pgjdbc/compare/REL42.7.9...REL42.7.12">compare view</a></li> </ul> </details> <br />
KofTwentyTwo (Migrated from github.com) reviewed 2026-10-15 01:46:18 +00:00
Checking for merge conflicts…
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin dependabot/maven/maven-55f3996f77:dependabot/maven/maven-55f3996f77
git checkout dependabot/maven/maven-55f3996f77
Sign in to join this conversation.