This is another entry on my bi-weekkly update about the AsyncAPI Spec and parsers.

Note This is not an official AsyncAPI update but a personal summary I volunteer to do.

What do I mean by AsyncAPI Spec ecosystem? As most of the work around the AsyncAPI Spec is not only related with, each update will include the most significant recent activity from the following repositories, which I consider them to be part of the same ecosystem:

Feel free to ask me to include any other repository if you consider it makes sense. Also, in case you want to help me with these updates :)


Spec v2.3.0 work is at 80%!

Those are the PR’s that have been merged and are gonna also be included in 2.3.0 version ๐ŸŽ‰:

At the same time, Dale Lane did some new additions to the release notes that will be published in the AsyncAPI blog. See the PR here.

And whats that 20% left?

feat: add security at the operation level by sekharbans PR had a lot of activity. In fact, we dedicated a SIG meeting to this topic. The reason is that there was (and still is) uncertainty about the fact Security requirements declared at Operation level should or shouldn’t inherit requirements from Server level. Please join the discussion on the PR so we can unblock it and move forward. The following PR’s are opened and feedback/review is wanted!:

There is some uncertainty about this feature to be included in 2.3.0, as always, better to not rush and take decissions after giving few rounds.

Spec v3.0.0 work is slowly progressing!

As always, You can find some of the most critical progress on the AsyncAPI spec v3.0.0 release journal

Work on the Parser-API has been initiated.

Jonas Lagoni is analysing all the API by trying to implement it in a mock version of the Parser-JS. The plan is to quickkly iterate over the Parser-API spec definition and accommodate all the missing features. Thanks to that work, some issues have been created:

Some docs are being changed as well in this draft PR by Sergio Moya at the same time we prepare everything for the v3.0.0 release in terms of CI here.

๐Ÿ—“ Something important to mention: a dedicated meeting for community members involved in works related with this release has been scheduled. See

You can find a list (grooming pending) of candidates to be included in v3.0.0 at

Spec also had some more activity

A new feature for the Solace binding has landed as a PR

feat: add topicSubscriptions to direct destinations by Michael Davis has some +1 already. However, eyes are always welcomed! ๐Ÿ‘€

Does Socket.IO binding an interesting feature for you?

Socket.IO protocol support is looking for a champion! ๐Ÿฆธ๐Ÿฟโ€โ™€๏ธ๐Ÿฆธ๐Ÿฝโ€โ™‚๏ธ

avro-schema-parser v1.0.1 got released!

It includes an important bugfix for the following issues:

The PR containing the bugfix can be found here.

There is also a small but needed refactor that reduces cognitive complexity. The PR (merged) can be found here.

I want to say thanks ๐Ÿ™๐Ÿพ to Jonathan for all the work it did on this project.

converter-js v0.6.1 got released!

It includes an important security fix that fixes few vulnerabilities. See fix: security vulnerabilities by [](Maciej Urbaล„czyk).

parser-js v1.13.2 got released!

It includes the following bugfix: fix: missing constructor type definition by Dominik Schwank.

More news around parser-js

Ritik Rawal is championing Throw meaningfull error when parser of specific schemaFormat is not available ๐Ÿ’ช



Commits by repo: Commits by repo

# Commits# Authors# Repositories
RepositoryCommitsAuthorsOrganizationsAdded LinesRemoved LinesAvg. LInes/CommitAvg. Files/Commit,9912661,125.72.1,0877,1472,404.251.75


Issues closed by repo

Issues closed by repo

Issues by status

# Issues# Submitters# AssigneesMedian Time Open (Days)
Repository# Issues Open# Submitters# Assignees# Labels

Pull Requests

Pull Requests opened: Pull Requests opened

Pull Requests closed: Pull Requests closed

Pull Requests by status

# Pull Requests# Submitters# Repositories
RepositoryPull RequestsSubmittersAssigneesAvg. Days Open