Back to Explore

asyncapi/spec-json-schemas

GitHub
1 watchersOpen source

Last release:

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 source appears actively maintained, with an upstream GitHub push on 2026-07-30 and recent tagged updates up through v6.11.1 (2026-01-30).
  • Update cadence looks moderate rather than continuous, with tagged updates clustered around early 2026 (v6.11.0 and v6.11.1 on 2026-01-30) and the next earlier tagged update on 2025-08-17, implying several-month gaps between tags even though commits continue.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

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.

    Features

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

  • v6.9.0

    Release v6.9.0 primarily adds new AsyncAPI JSON schema support for ROS 2 bindings (v0.1.0). The code diff also includes additional schema constraint updates (including SQS and the core 3.0.0 message schema), plus a range of CI/workflow and dev-dependency updates that are not mentioned in the release notes.

    Features

  • v6.8.1

    Release v6.8.1 is documented as a single bug fix for MessageExample payload typing. However, the actual diff includes significant repository-level changes, including a test runner migration (mocha to vitest), dependency updates, and a large addition of new schema validation tests.

  • v6.8.0

    v6.8.0 release notes document a single change: extending AWS policy configuration. However, the code diff shows substantially more than that, including new SNS and SQS binding schemas, CI workflow environment changes, and dev dependency updates.

    Features

  • v7.0.0-next-major.2

    v7.0.0-next-major.2 is described as removing duplicate schemas. The code diff indicates this is implemented both in the bundling script logic (changing where common schemas live and which directories are processed) and by removing multiple concrete schema JSON files from the package.

    Breaking

  • v7.0.0-next-major.1

    v7.0.0-next-major.1 is a breaking release that removes the AsyncAPI 2.0.0 release candidate schema artifacts for rc1 and rc2. The code diff shows large-scale deletion of JSON schema definition files for those versions, rather than incremental changes.

    Breaking

  • v6.7.1

    v6.7.1 is primarily a JSON schema change that factors the message example shape into a dedicated definition object. The diff also includes additional, non-release-note changes affecting LinkedIn URL validation and some repository GitHub workflow automation.

  • v6.7.0

    This release adds support for a new AsyncAPI extension, x-linkedin, intended to carry a LinkedIn profile URL. The schemas for AsyncAPI 3.0.0 and 3.0.0-without-$id were updated to include the new extension definition and reference.

    Features