Bump jooqVersion from 3.20.10 to 3.20.11

[dependabot]

Bumps jooqVersion from 3.20.10 to 3.20.11.
Updates org.jooq:jooq-codegen-gradle from 3.20.10 to 3.20.11

Release notes

Sourced from org.jooq:jooq-codegen-gradle's releases.

3.20.11

Version 3.20.11 - January 29, 2026

This is a 3.20 patch release with minor improvements and bug fixes

Bug Fixes

#19484 - Work around DuckDB limitation where RETURNING clauses don't support bind values #19487 - DuckDB doesn't support the ON CONFLICT .. WHERE clause, only the DO UPDATE .. WHERE clause #19495 - Error with DuckDB DECIMAL bind value cast for large decimals #19499 - Work around DuckDB limitation of not being able to qualify UDT arrays #19500 - Cannot bind UDT arrays in DuckDB #19502 - JSON parser should be able to handle non-standard JSON NaN and Infinity values #19506 - Confusing warning about dialect version support #19510 - DuckDB doesn't support binding lobs in ClobBinding #19513 - DuckDBDatabase produces both identity flags and DEFAULT expression #19517 - Multiset JSON emulation should use explicit JSON_ARRAYAGG .. ORDER BY clause where derived table ordering is unstable #19520 - Bad DuckDB interval bind values formatting #19522 - Bad decoding of spatial data from DuckDB database #19525 - Bad cast type for DuckDB INTERVAL DAY TO SECOND type #19528 - Bad date time arithmetic rendered for DuckDB DATE + INTERVAL expressions #19535 - Optimistic locking may produce unsupported FOR UPDATE clause in DuckDB #19538 - DuckDB NestedCollectionEmulation.JSON emulation can't nest MULTISET expressions in ROW expressions #19541 - Add support for DuckDB TIMESTAMP_NS, TIMESTAMP_MS, TIMESTAMP_S types #19546 - DuckDBDatabase shouldn't use INFORMATION_SCHEMA.KEY_COLUMN_USAGE.POSITION_IN_UNIQUE_CONSTRAINT #19552 - Upgrade log4j-core dependency to mitigate CVE-2025-68161 #19559 - Error when using IS [NOT] DISTINCT FROM with LOB columns in Oracle #19564 - Meta.getTables(Name) should allow for partially qualified lookups #19573 - HSQLDBDatabase doesn't correctly implement includeSystemCheckConstraints when identifiers are quoted #19580 - Bad formatting of CAST() function content #19585 - QOM.Array should implement SimpleCheckQueryPart, and return true if there are only few elements #19592 - SortFieldImpl should implement ComplexCheckQueryPart to delegate formatting decisions to contents #19595 - Improve formatting of PARTITION BY and ORDER BY clauses in window functions #19598 - SQLExceptionLoggerListener logs incorrect message about precision when truncated numeric value cannot be inserted for some other reason #19603 - Support emulating EXCLUDED in MySQL, when used in expressions #19607 - MULTISET returns invalid JSONB for JSON string scalar values #19611 - Inlined JSON should be rendered as JSON literal in DuckDB #19616 - Unable to disable generation of implicit many-to-many path methods #19622 - jOOQ-bom pom.xml should be published using packaging=pom

Commits

• 9b8a104 Release 3.20.11
• fd47c09jOOQ/jOOQ#19621
• 6186acajOOQ/jOOQ#19614
• 7c27f54jOOQ/jOOQ#19606
• 7ff8e98jOOQ/jOOQ#19610
• a8f3507jOOQ/jOOQ#19606
• 9c65220jOOQ/jOOQ#16942
• 30dd29ajOOQ/jOOQ#19591
• 99e6b1ejOOQ/jOOQ#19584
• a72a52bjOOQ/jOOQ#19584
• Additional commits viewable in compare view

Updates org.jooq:jooq-meta from 3.20.10 to 3.20.11

Updates org.jooq:jooq-postgres-extensions from 3.20.10 to 3.20.11

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[lfdt-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for e167c8d1	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (e167c8d)	Report Missing	Report Missing	Report Missing
Head commit (b9aa3ed)	52853	28909	54.70%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#12869)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩