[dependabot]

Bumps com.networknt:json-schema-validator from 3.0.2 to 3.0.8.

Release notes

Sourced from com.networknt:json-schema-validator's releases.

3.0.8- 2026-09-30

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)

3.0.7- 2026-08-20

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

3.0.6- 2026-07-07

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

3.0.5- 2026-06-21

Added

Changed

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

... (truncated)

Changelog

Sourced from com.networknt:json-schema-validator's changelog.

Change Log

All notable changes to this project will be documented in this file.

This format is based on Keep a Changelog.

This project does not adhere to Semantic Versioning and minor version changes can have incompatible API changes. These incompatible API changes will largely affect those who have custom validator or walker implementations. Those who just use the library to validate using the standard JSON Schema Draft specifications may not need changes.

[Unreleased]

Added

• Opt-in ExecutionConfig.maxEvaluationSteps and maxEvaluationDepth limits for validation and schema walking, including walking without assertions. Exhaustion throws ValidationLimitExceededException instead of returning a partial validity result. Both limits default to unlimited; they bound admitted evaluation steps and schema frames, not work inside a keyword. (#1276)

Changed

• Without Ethlo on the classpath, the date-time format now checks the date with the rules of the date format and the time with the rules of the time format instead of OffsetDateTime.parse(..). It rejects a time without seconds (2020-01-01T12:00Z), an offset without minutes (+01) and an empty fraction (12:00:00.Z), which Ethlo already rejected, as well as an offset with seconds (+01:00:00). It accepts an offset up to 23:59 and a fraction longer than nine digits, which RFC 3339 allows, and a leap second at the end of a June 30 or a December 31 in UTC, which it used to reject. Compared with Ethlo, the fallback provides less accurate leap-second validation because it does not check that a leap second was actually inserted on that date. It also accepts -00:00, offsets beyond ±18:00, and fractions longer than nine digits, which Ethlo rejects. The fallback requires T or t between the date and time, rejecting a space separator such as 2020-01-01 12:00:00Z that Ethlo accepts. (#1316, #1337)
• The time format now rejects a leap second with an hour or minute out of range (24:59:60+01:00, 23:89:60+00:30, 45:59:60+22:00), which it used to accept. A time without seconds (12:00Z) was already rejected. (#1316, #1337)
• Ignore zero multipleOf divisors returned by custom validators, regardless of scale, matching the default conversion. (#1328)
• Display multipleOf divisors in error messages using plain notation when it fits within 32 characters or is no longer than BigDecimal.toString(), including values returned by custom validators. Check the length before expanding to plain notation to avoid excessive padding for extreme scales. (#1328)
• MultipleOfValidator.getDivisor and getDividend now preserve exact integral and BigDecimal values. Custom validators, including overrides calling super, receive these exact values; validation uses hook results without further rounding. Integral dividend scales can change (for example, 2.0 becomes 2), which affects scale-sensitive comparisons in overrides. Mixed integral/Double or Float inputs above 2^53 can produce different results. Precision already lost when parsing floating-point values is tracked separately in #1293. (#1286)
• Extend document-root unknown-keyword suppression to external $ref JSON Pointer targets. Keep container and direct-schema caches separate so direct registry loads retain normal diagnostics regardless of registry load order, including rejection by DisallowUnknownKeywordFactory. Within one schema, a whole-document reference following a JSON Pointer reference can still reuse the container and suppress root diagnostics, including strict-factory rejection. Apply the container annotation fallback after nullable/discriminator special handling and make the container marker volatile. (#1325)
• Treat unknown document-root fields as annotations when loading a schema by JSON Pointer fragment, while preserving known keyword processing and diagnostics in subschemas. With DisallowUnknownKeywordFactory, such fragment loads now succeed instead of throwing on unknown root fields; direct document loads still throw. If the selected schema references the root with $ref: "#", unknown root fields also remain annotations and do not reach the unknown-keyword factory. (#1205)
• Unlimited validation/walking bypasses execution counters and keeps the original recursion frame structure. During an active limited execution, reentrant convenience calls share the budget and the caller's evaluation path; unlimited calls retain their legacy root-path initialization.
• Exhausted contexts reject public errors/annotation access. Walk listeners can inspect ExecutionContext.isEvaluationAborted() and getEvaluationAbort() during cleanup; an empty error slice after abort is not a validity verdict. Subclass builders supporting limits must use the protected builder constructor or forward both limits explicitly, since the legacy seven-argument constructor remains unlimited.
• Error.getMessageKey() now returns the message key when the schema supplies a custom message, such as type or required, instead of the custom message text. Unresolved $ref, $dynamicRef and $recursiveRef errors return internal.unresolvedRef instead of Reference {0} cannot be resolved. Use getMessage() for the text and isCustomMessage() to detect custom messages. Errors created without a key still use their message pattern as the key. (#1319)

3.0.8- 2026-09-30

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)

3.0.7- 2026-08-20

Added

Changed

• fixes #1277 upgrade jackson to 3.2.1 to resolve a security vulnerability

... (truncated)

Commits

• 12596e6 upgrade to 3.0.8 and update changelog
• 759445b upgrade slf4j to 2.0.19 from 2.0.17
• f26327c upgrade maven-surefire to 3.6.0
• 2575a02 upgrade logback to 1.6.3 from 1.5.37
• 3d9971d upgrade logback to 1.5.37
• 6f5d6c1 upgrade actions/checkout
• 4649209 upgrade central-publishing-maven to 0.11.0 from 0.7.0
• dc11f65 Port the nullable ancestor walk from the 2.x branch (#1283)
• 3c433c4 Add YAML non-finite number regression test for #1228 (#1282)
• 81efb27 Honor PathType when formatting DiscriminatorValidator schema locations (#1281)
• Additional commits viewable 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @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)

[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: a8a0cbf9-304b-40da-b954-ac3579c7852f

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

• Autofix · 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.}