ecommerce-microservices-spring-reactive-webflux
ecommerce-microservices-spring-reactive-webflux copied to clipboard
Bump postgresql from 42.4.1 to 42.4.3 in /system/authentication
Bumps postgresql from 42.4.1 to 42.4.3.
Release notes
Sourced from postgresql's releases.
v42.4.3
What's Changed
- backpatch 42.5.1 by
@davecramerin pgjdbc/pgjdbc#2675Full Changelog: https://github.com/pgjdbc/pgjdbc/compare/REL42.4.2...REL42.4.3
v42.4.2
What's Changed
- Revert revert commits made in PR 2580 by
@davecramerin pgjdbc/pgjdbc#2583- fix: make setObject accept UUID array by
@sasavilicin pgjdbc/pgjdbc#2587- fix mismatched types for invokeExact. Have to tell invokeExact what type we are expecting by
@davecramerin pgjdbc/pgjdbc#2589- update last copyright year by
@davecramerin pgjdbc/pgjdbc#2593- fix erroneous method signature and null subjectCallAs by
@davecramerin pgjdbc/pgjdbc#2595- Update changelog for release by
@davecramerin pgjdbc/pgjdbc#2596New Contributors
@sasavilicmade their first contribution in pgjdbc/pgjdbc#2587Full Changelog: https://github.com/pgjdbc/pgjdbc/compare/REL42.4.1...REL42.4.2
Changelog
Sourced from postgresql's changelog.
Changelog
Notable changes since version 42.0.0, read the complete History of Changes.
The format is based on Keep a Changelog.
[Unreleased]
Changed
Added
Fixed
[42.6.0] (2023-03-17 15:34:34 -0400)
Changed
fix: use PhantomReferences instead of
Obejct.finalize()to track Connection leaks [PR #2847](pgjdbc/pgjdbc#2847)The 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](pgjdbc/pgjdbc#2635) Fixes [Issue #1951](pgjdbc/pgjdbc#1951)
[42.5.4] (2023-02-15 10:21:04 -0500)
Fixed
fix: fix testGetSQLTypeQueryCache by searching for xid type. We used to search for box type but it is now cached. xid is not cached, this nuance is required for the test. fix OidValueCorrectnessTest BOX_ARRAY OID, by adding BOX_ARRAY to the oidTypeName map [PR #2810]((pgjdbc/pgjdbc#2810). fixes [Issue #2804](pgjdbc/pgjdbc#2804). fix: Make sure that github CI runs tests on all [PRs #2809]((pgjdbc/pgjdbc#2809)).
[42.5.3] (2023-02-03 08:24:50 -0500)
Fixed
fix: Add box to TypeInfoCache, fixes [Issue #2746](pgjdbc/pgjdbc#2746) [PR #2747](pgjdbc/pgjdbc#2747) fix: regression in PgResultSet LONG_MIN copy and paste error fixes [Issue #2748](pgjdbc/pgjdbc#2748) PR#2749
[42.5.2] (2023-01-31 14:30:46 -0500)
Changed
regression: This release has 2 known regressions which make it unusable see the notes above. We advise people to use 42.5.3 instead. docs: specify that timeouts are in seconds and there is a maximum. Housekeeping on some tests fixes #Issue 2671 [PR #2686](pgjdbc/pgjdbc#2686) docs: clarify binaryTransfer and add it to README PR# 2698 docs: Document the need to encode reserved characters in the connection URL [PR #2700](pgjdbc/pgjdbc#2700) feat: Define binary transfer for custom types dynamically/automatically fixes [Issue #2554](pgjdbc/pgjdbc#2554) [PR #2556](pgjdbc/pgjdbc#2556)
Added
fix: added gssResponseTimeout as part of [PR #2687](pgjdbc/pgjdbc#2687) to make sure we don't wait forever on a GSS RESPONSE
Fixed
... (truncated)
Commits
34855cfbackpatch 42.4.x for changes to 42.5.1 (#2675)389be0aUpdate changelog for release (#2596)364662efix erroneous method signature and null subjectCallAs (#2595)04dc96aupdate last copyright year (#2593)f76ca46fix checkstylea45b4d8get rid of javadoc warningsabf3bcbfix mismatched types for invokeExact. Have to tell invokeExact what type we a...96f2561fix: make setObject accept UUID array (#2587)0b097fdbumped minor version for next release7363fffRevert revert commits made in PR 2580 (#2583)- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.