AsyncAPI spec-json-schemas provides JSON Schema documents for validating AsyncAPI documents across different AsyncAPI specification versions, with schema variants that include or omit the JSON Schema `$id` behavior. It also includes JavaScript and Go modules to access these schema files from code, useful when you need versioned schema-based validation in your tooling.
Project status
- The
asyncapi/spec-json-schemasGitHub source shows ongoing activity, with an upstream push on 2026-07-30, but the latest publishedupdatesin the provided history are older (v6.11.1 and v6.11.0 on 2026-01-30), suggesting maintenance with fewer tagged releases than commits. - Apparent release/update cadence: two consecutive versioned
updateson 2026-01-30 (v6.11.0, v6.11.1), then the prior documented version is v6.10.0 on 2025-08-17, indicating a roughly multi-month cadence between tagged schemaupdates.
AI summary generated
Recent updates
v6.11.1
Release v6.11.1 contains a small update described as “update ros2 related schemas”. The code diff shows several schema-level changes affecting AsyncAPI 3.1.0 resolution and ROS2 binding schemas, including changes to required properties and reference targets for specification extensions.
v6.11.0
v6.11.0 adds AsyncAPI 3.1.0 JSON schema support and introduces initial ROS 2 binding schemas under bindings/ros2/0.1.0. The release notes only mention the ROS 2 binding and AsyncAPI 3.1.0, but the diff also includes substantial CI/CD workflow and dependency updates.
Featuresv6.10.0
v6.10.0 is described as a revert of the previously added ROS2 bindings. The code diff, however, shows ROS2 schema content is not simply removed, it is re-packaged and partially removed, with ROS2 operation bindings dropped and ROS2 server bindings inlined into the main monolithic schemas.
Breaking