[mwadams]

What kind of change does this PR introduce?

A tooling data update for Corvus.JsonSchema.

Issue Number:

• Closes Modify Corvus.JsonSchema in JSON Schema Ecosystem #2527

Screenshots/videos:

None: this changes data/tooling-data.yaml only.

If relevant, did you update the documentation?

Not applicable.

Summary

Corvus.JsonSchema's runtime evaluator is now published for seventeen languages:

Language	Package
.NET	Corvus.Text.Json on NuGet
TypeScript and JavaScript	@corvus-dotnet/json-schema on npm
Rust	corvus-json-schema on crates.io
Python	corvus-json-schema and corvus-json-schema-rs on PyPI
Java and Kotlin	io.github.corvus-dotnet:corvus-json-schema on Maven Central
Go	github.com/corvus-dotnet/Corvus.JsonSchema/src-go/corvus-json-schema
C and C++	the corvus-json-schema C library and its C++17 wrapper (releases)
Swift	CorvusJsonSchema, for Swift Package Manager
Ruby	corvus_json_schema on RubyGems
PHP	corvus-dotnet/corvus-json-schema on Packagist
Julia	CorvusJsonSchema in the General registry
R	corvusjsonschema on R-universe
Object Pascal	a Free Pascal source package (releases)
OCaml	corvus-json-schema, an opam package

Each runs the JSON-Schema-Test-Suite for draft 4, 6, 7, 2019-09 and 2020-12, and draft 4 is supported as fully as the later drafts.

• The validator entry:
  • lists those languages in languages (R, Object Pascal, OCaml and C are not in the schema's list, which allows other names; C is the spelling another entry uses);
  • names the packages in its description, and says how draft 4 is supported;
  • adds draft 4 to supportedDialects;
  • updates lastUpdated to the date of the latest release.
• The schema-to-code entry: adds draft 4 to supportedDialects, which the code generator also supports.

The tooling page's Bowtie badges for the validator entry come from the existing source URL, which matches the V5 engine (dotnet-corvus-jsonschema-v5engine) in Bowtie's report, so no Bowtie field is needed. That report also lists draft 4.

data/tooling-data.yaml validates against data/tooling-data.schema.json with the same Ajv check as validate-tooling-data.yml. The branch is rebased on main.

Does this PR introduce a breaking change?

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	aa4ab7e

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9c4a017) to head (aa4ab7e).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #2528   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           31        31           
  Lines          719       719           
  Branches       224       224           
=========================================
  Hits           719       719           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[garv-sanveria]

Review type: Read-only

Thanks for updating the tooling data for Corvus!

Actionable Suggestion: Since you added support for Draft 4, which is quite an old specification, it might be worth explicitly stating in the description if there are any caveats or if it is 100% fully supported.

Question: Just out of curiosity, I see the lastUpdated date was bumped to 2026-10-01. Do you usually use the date the PR is opened, or the date of the actual tool's release?

[mwadams]

Review type: Read-only

Thanks for updating the tooling data for Corvus!

Actionable Suggestion: Since you added support for Draft 4, which is quite an old specification, it might be worth explicitly stating in the description if there are any caveats or if it is 100% fully supported.

Question: Just out of curiosity, I see the lastUpdated date was bumped to 2026-10-01. Do you usually use the date the PR is opened, or the date of the actual tool's release?

Sorry it took me a while to notice your review comment.

I usually use the PR date, because we issue fairly frequent updates and we wouldn't PR every one in here.

I have just updated the tooling list to include our latest language releases that have come out since this PR was initially opened, to avoid having to go through the loop again.