Skip to content

Update dependency com.networknt:json-schema-validator to v2.0.8 - #36

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/networknt-validator.version
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/networknt-validator.version

Conversation

@renovate

@renovate renovate Bot commented Sep 6, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
com.networknt:json-schema-validator 2.0.1 → 2.0.8 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Have a look at your dependency dashboard


Release Notes

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

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

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.


Configuration

📅 Schedule: (in timezone Australia/Sydney)

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

@renovate
renovate Bot force-pushed the renovate/networknt-validator.version branch from 595fe45 to dae4cce Compare October 4, 2026 16:42
@renovate renovate Bot changed the title Update dependency com.networknt:json-schema-validator to v2.0.7 Update dependency com.networknt:json-schema-validator to v2.0.8 Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants