fix(deps): update dependency com.networknt:json-schema-validator to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.networknt:json-schema-validator	1.5.9 → 3.0.8

---

Release Notes

networknt/json-schema-validator (com.networknt:json-schema-validator)

v3.0.8

Compare Source

Added

Changed

• Expose Error.isCustomMessage() to identify messages supplied by the schema through the configured error message keyword, while preserving the existing Error constructor's binary compatibility and JSON serialization format. (680d7b3, f8c7659)
• Reject leading or interior empty labels and names consisting only of label separators in the idn-hostname format (#​1274) Thanks @​dngr2
• Allow apostrophes in uri-template literals (#​1275) Thanks @​dngr2
• Honor PathType when formatting schema locations in DiscriminatorValidator exceptions (#​1281) Thanks @​youdie006
• Resolve the OpenAPI nullable keyword through allOf/oneOf/anyOf, if/then/else and $ref/$dynamicRef/$recursiveRef ancestors, to any depth and in any order. nullable on a schema composed through these keywords now applies to the value they describe, for both the type and enum keywords (#​1278, #​1279, #​1283) Thanks @​tomakehurst
• nullable on a container no longer applies to the values described by its properties, items and additionalProperties subschemas. Previously a nullable container made its children accept null. Schemas relying on that must declare nullable on the child itself. (#​1283) Thanks @​tomakehurst
• oneOf no longer requires exactly one matching branch when the value is null and a nullable ancestor permits it. Every branch accepts null in that case, so {"nullable": true, "oneOf": [ ... ]} previously reported that more than one branch matched. Branch errors are still reported when no branch matches. (#​1283) Thanks @​tomakehurst
• nullable no longer applies inside a not subschema, so {"nullable": true, "not": {"type": "string"}} now accepts null where it previously reported a not error. (#​1283) Thanks @​tomakehurst
• With typeLoose enabled, the empty string no longer satisfies an enum on a nullable schema. null was previously held in the accepted set and compared as text, where it renders as the empty string, so {"enum": ["a"], "nullable": true} accepted "". Only an actual null is accepted now. (#​1283) Thanks @​tomakehurst
• A nullable declared alongside $ref is now ignored at the root of an OpenAPI 3.0 schema as it already was elsewhere, so {"$ref": "...", "nullable": true} rejects null. Siblings of a Reference Object are ignored in OpenAPI 3.0. (#​1283) Thanks @​tomakehurst
• Add regression coverage for YAML .nan, .inf and -.inf values producing validation type errors instead of parser exceptions with Jackson 3.2.1 (#​1228, #​1282) Thanks @​patpatpat123
• Upgrade SLF4J from 2.0.17 to 2.0.19 and the test dependency Logback from 1.5.22 to 1.6.3. (759445b, 3d9971d, 2575a02)
• Upgrade Maven Surefire and Surefire Report from 3.5.4 to 3.6.0, and the Central Publishing Maven plugin from 0.7.0 to 0.11.0. (f26327c, 4649209)
• Upgrade the benchmark workflow to actions/checkout@v7 and actions/setup-java@v6. (6f5d6c1)

v3.0.7

Compare Source

Added

Changed

• fixes #​1277 upgrade jackson to 3.2.1 to resolve a security vulnerability
• ix: uniqueItems compares numbers by value, not by node type (#​1273) Thanks @​dngr2
• Honor PathType when formatting SchemaException locations (#​1272) Thanks @​kalayciburak
• Reject non-ASCII whitespace in idn-email and format tests (#​1268) Thanks @​el-psy-kongroo-d
• Reject non-ASCII whitespace in email format (#​1267) Thanks @​el-psy-kongroo-d

v3.0.6

Compare Source

Added

Changed

• Fall back to the library class loader for classpath resources (#​1265) Thanks @​joaodinissf
• Add schema tests (#​1260) (#​1261) Thanks @​gjvoosten
• Bump jackson to 3.1.4 to fix CVE-2026-54512 and CVE-2026-54513 (#​1263) Thanks @​olinoskar
• Reduce per-validation allocation in ExecutionContext (#​1259) Thanks @​nishantmehta
• test: re-enable and strengthen recursive $ref SelfRefTest (#​1258) Thanks @​koteshyelamati
• simplify additionalItems validation flow (#​1256) Thanks @​Oz-er

v3.0.5

Compare Source

Added

Changed

• fixes #​1252 problem with additionalProperties schema in jsconfig schema (#​1253)
• fixes #​1174 TextNodes as schema seem to validate any value (#​1250)

v3.0.4

Compare Source

Added

Changed

• fixes #​1248 validating draft4 schemas (#​1249)

v3.0.3

Compare Source

Added

Changed

• fixes #​1246 Coercion bug (#​1247)
• Cleanup of IOException leftovers after update to jackson3 (#​1244) Thanks @​afiluba

v3.0.2

Compare Source

Added

Changed

• Upgrade Jackson from 3.1.0 to 3.1.1 to fix CWE-770 (#​1236) Thanks @​cjun-coveo
• Support handling of non-finite numbers if present (#​1241) Thanks @​justin-tay

v3.0.1

Compare Source

Added

Changed

• Upgrade Jackson from 3.0.3 to 3.1.0 to fix CVE-2026-29062 (#​1236) Thanks @​AhsanSheraz
• Fix minimum maximum validators with type array (#​1227) Thanks @​justin-tay
• Add method to SpecificationVersion to determine from schema node (#​1221) Thanks @​justin-tay
• update contributor list in README.md

v3.0.0

Compare Source

Added

Changed

• Upgrade to Jackson 3 and JDK 17 (#​1219) Thanks @​justin-tay

v2.0.8

Compare Source

2.0.8- 2026-10-01

Added

Changed

• Resolve the OpenAPI nullable keyword through allOf/oneOf/anyOf, if/then/else and $ref/$dynamicRef/$recursiveRef ancestors, to any depth and in any order. nullable on a schema composed through these keywords now applies to the value they describe, for both the type and enum keywords.
• nullable on a container no longer applies to the values described by its properties, items and additionalProperties subschemas. Previously a nullable container made an inline (non-$ref) child accept null. Schemas relying on that must declare nullable on the child itself.
• oneOf no longer requires exactly one matching branch when the value is null and a nullable ancestor permits it. Every branch accepts null in that case, so {"nullable": true, "oneOf": [ ... ]} previously reported that more than one branch matched. Branch errors are still reported when no branch matches.
• nullable no longer applies inside a not subschema, so {"nullable": true, "not": {"type": "string"}} now accepts null where it previously reported a not error.
• With typeLoose enabled, the string "null" no longer satisfies an enum on a nullable schema. {"enum": ["a"], "nullable": true} previously accepted the string "null" as well as an actual null; only an actual null is accepted now.

v2.0.7

Compare Source

2.0.7- 2026-08-20

Added

Changed

• Preserve binary compatibility for the Error constructor after adding custom-message metadata.

GitHub tag correction: this tag previously pointed to a 3.x commit on master. It now points to the verified 2.x release commit ae64ed637f743c4a88b2a391f20b639fe7f7d8e3, whose POM and all 222 published Java source files match Maven Central. The published Maven artifacts were already correct.

v2.0.6

Compare Source

2.0.6- 2026-08-20

Added

• Add Error.isCustomMessage() to identify schema-supplied validation messages.

Changed

Restored missing GitHub tag and release. The release commit was verified against the existing Maven Central POM and all 222 published Java source files.

v2.0.5

Compare Source

2.0.5- 2026-08-20

Added

Changed

• upgrade jackson to 2.22.1 to resolve a security vulnerability

GitHub tag correction: this tag previously pointed to a 3.x commit on master. It now points to the verified 2.x release commit 1fedf7133bb9ba4b41c7e3575abea01a6d5b61d0, whose POM and all 222 published Java source files match Maven Central. The published Maven artifacts were already correct.

v2.0.4

Compare Source

2.0.4- 2026-07-07

Added

Changed

• Fall back to the library class loader for classpath resources (#​1266) Thanks @​joaodinissf

GitHub tag correction: this tag previously pointed to a 3.x commit on master. It now points to the verified 2.x release commit 2ad25293fe9f28a43867b2e57fabb0a01f68317f, whose POM and all 222 published Java source files match Maven Central. The published Maven artifacts were already correct.

v2.0.3

Compare Source

2.0.3- 2026-06-23

Added

Changed

• release with JDK 11
• fixes 2.0.2 published jar is missing module-info.class — JPMS module com.networknt.schema no longer resolves

GitHub tag correction: this tag previously pointed to a 3.x commit on master. It now points to the verified 2.x release commit 8f2afe9090b1745b920fdbebf8f2a4f707eba0a5, whose POM and all 222 published Java source files match Maven Central. The published Maven artifacts were already correct.

v2.0.2

Compare Source

2.0.2- 2026-06-21

Added

Changed

• fixes #​1248 validating draft4 schemas (#​1249)

• fixes #​1248 validating draft4 schemas

• Address regex factory review comments

• Rename regex specification version variable

• fixes #​1174 TextNodes as schema seem to validate any value (#​1250)

• fixes #​1174 TextNodes as schema seem to validate any value

• Address loaded schema validation for issue 1174

• Address schema node validation review comments

• Preserve mapped schema override path

• Validate referenced document fragment schemas

• Remove duplicate schema type validation

• Validate loaded schemas for anchor refs

• fixes #​1252 problem with additionalProperties schema in jsconfig schema (#​1253)

• Add method to SpecificationVersion to determine from schema node (#​1221)

• Manual adjustments for Jackson 2 compatibility and CVE fix

GitHub tag correction: this tag previously pointed to a 3.x commit on master. It now points to the verified 2.x release commit a3e58d9e55754e940277d2a1342bb1d3c2061e69, whose POM and all 222 published Java source files match Maven Central. The published Maven artifacts were already correct.

v2.0.1

Compare Source

Added

Changed

• Skip processing of properties keyword if not an object (#​1217) Thanks @​justin-tay
• Allow for default dialect id not to be specified and throw an exception (#​1212) Thanks @​justin-tay
• Fix multipleOf error message for fractional digits greater than 3 (#​1210) Thanks @​justin-tay

v2.0.0

Compare Source

Added

Changed

• Fix ref with sibling id from 2019-09 (#​1203) Thanks @​justin-tay
• Refactor walk and update docs (#​1202) Thanks @​justin-tay
• Fix matching of $ when there are trailing newlines (#​1201) Thanks @​justin-tay
• Refactor evaluation context out from validator state (#​1199) Thanks @​justin-tay
• Main refactor for 2.x (#​1198) Thanks @​justin-tay
• Refactor set to list in execution context (#​1197) Thanks @​justin-tay
• Refactor and remove validation message handler (#​1196) Thanks @​justin-tay
• Add benchmark for performance regression testing (#​1195) Thanks @​justin-tay

---

Configuration

📅 Schedule: (UTC)

• 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 6642479c-1df1-44f1-818d-3a70af456667

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Pfeil]

see #333