Update Mend: high confidence minor and patch dependency updates #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
42.3.1->42.7.83.27.0-GA->3.30.2-GA4.0.0->4.5.00.9.1->0.13.01.21->1.331.18.20->1.18.424.1.4->4.1.51.10.2->1.21.23.9->3.173.10-FINAL->3.171.4.10->1.4.213.6->3.12.01.6.0->1.7.22.9.1->2.25.22.9.1->2.25.24.5.12->4.5.142.4->2.63.1->3.2.223.0->23.6.1-jre2.0.6->2.0.6.11.2.24->1.2.83_noneautotype8.0.12->8.0.331.5.1.RELEASE->1.5.22.RELEASERelease Notes
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.7.8Added
Changed
BufferedInputStreamwithFileInputStreamPR #3750Fixed
v42.7.7Security
Fix
channel binding requiredhandling to reject non-SASL authenticationPreviously, when channel binding was set to "require", the driver would silently ignore this
requirement for non-SASL authentication methods. This could lead to a false sense of security
when channel binding was explicitly requested but not actually enforced. The fix ensures that when
channel binding is set to "require", the driver will reject connections that use
non-SASL authentication methods or when SASL authentication has not completed properly.
See the Security Advisory for more detail. Reported by George MacKerron
The following CVE-2025-49146 has been issued
Added
v42.7.6Features
Performance Improvements
v42.7.5Added
Fixed
fc60537PR #3476v42.7.4Added
Fixed
Deprecated
v42.7.3Changed
Fixed
else iftoswitchNoSuchMethodError on ByteBuffer#positionwhen running on Java 8v42.7.2Security
SimpleQuerymode to generate a line comment by having a placeholder for a numeric with a-such as
-?. There must be second placeholder for a string immediately after. Setting the parameter to a -ve value creates a line comment.This has been fixed in this version fixes CVE-2024-1597. Reported by Paul Gerste. See the security advisory for more details. This has been fixed in versions 42.7.2, 42.6.1 42.5.5, 42.4.4, 42.3.9, 42.2.28.jre7. See the security advisory for work arounds.
Changed
Added
v42.7.1Changed
Fixed
Fixes Issue #3008
Fixes Issue #3007
,Issue #2850
Closes [Issue #1391(#1391)
v42.7.0Changed
java.desktopmodule. PR #2967Fixed
v42.6.0Changed
fix: use PhantomReferences instead of
Obejct.finalize()to track Connection leaks PR #2847The change replaces all uses of Object.finalize with PhantomReferences.
The leaked resources (Connections) are tracked in a helper thread that is active as long as
there are connections in use. By default, the thread keeps running for 30 seconds after all
the connections are released. The timeout is set with pgjdbc.config.cleanup.thread.ttl system property.
refactor:(loom) replace the usages of synchronized with ReentrantLock PR #2635
Fixes Issue #1951
v42.5.4Fixed
v42.5.3Fixed
v42.5.2Changed
Added
Fixed
v42.5.1Security
This has been fixed in this version fixes CVE-2022-41946 see the security advisory for more details. Reported by Jonathan Leitschuh This has been fixed in versions 42.5.1, 42.4.3 42.3.8, 42.2.27.jre7. Note there is no fix for 42.2.26.jre6. See the security advisory for work arounds.
Fixed
v42.5.0Changed
float now aliases to float8 PR #2598 fixes Issue #2597
v42.4.2Changed
Added
Fixed
v42.4.1Security
SQL. This allowed a malicious table with column names that include statement terminator to be parsed and
executed as multiple separate commands.
Changed
Added
v42.4.0Changed
startup parameters in a transaction (default=false like 42.2.x) fixes Issue #2425
pgbouncer cannot deal with transactions in statement pooling mode PR #2425
Fixed
PR #2525, Issue #1311
Regression since 42.2.13. PR #2531, issue #2527
v42.3.6Changed
Added
Fixed
v42.3.5Changed
Added
Fixed
This is a regression from 42.2.x versions where tcpNoDelay defaulted to true
v42.3.4Changed
and default timezones PR 2464 fixes Issue #2221
Added
Fixed
v42.3.3Changed
They can no longer be used to configure the driver logging. Instead use java.util.logging
configuration mechanisms such as
logging.properties.Added
Fixed
v42.3.2Security
sslhostnameverifier, socketFactory, sslfactory, sslpasswordcallback connection properties.
However, the driver did not verify if the class implements the expected interface before instantiating the class. This
would allow a malicious class to be instantiated that could execute arbitrary code from the JVM. Fixed in commit
Changed
is prefer or require PR #2396 remove the need to have a ticket in the cache before asking the server if gss encryptions are supported
or JDBC 4.2.
CallableStatement#getBoolean(int) on BIT(>1).
Changes internal constructors for PgConnection and related classes to only accept the connection properties object and
remove the user and password arguments. Any locations that required those fields can retrieve them from the properties map.
Added
Adds authenticationPluginClassName connection property that allows end users to specify a class
that will provide the connection passwords at runtime. Users implementing that interface must
ensure that each invocation of the method provides a new char[] array as the contents
will be filled with zeroes by the driver after use.Call sites within the driver have been updated to use the char[] directly wherever possible.
This includes direct usage in the GSS authentication code paths that internally were already converting the String password into a char[] for internal usage.
This allows configuring a connection with a password that must be generated on the fly or periodically changes. PR #2369 original issue Issue #2102
Fixed
fixes Issue #921 synchronize modification of shared calendar
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.