Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(blog): release notes for 2.1 release #260

Merged
merged 18 commits into from
Jun 29, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 14 additions & 5 deletions pages/blog/release-notes-2.1.0.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: AsyncAPI Spec 2.1.0 Release Notes
date: 2021-06-30T06:00:00+01:00
date: 2021-06-25T06:00:00+01:00
type: Communication
tags:
- specification
Expand All @@ -17,15 +17,17 @@ featured: true

The last, 2.0.0 AsyncAPI release took place on 11th of September, 2019. In 2020 the focus went into the direction of growing community and adoption and stabilizing basing tooling supporting specification. This year it was a year of "formalizm" 😃 aka getting into foundation, setting up governance model and contrubition guide to enable work on next spec release. We are good to go forward. The 2.1.0 release is out in the wild 🎉

(TODO: not yet approved and merged) ## Examples object extended with additional fields
## Message examples object extended with additional fields

Thanks to support from [Laurent Broudoux](https://github.com/lbroudoux), you can now clearly describe message examples. New properties `name` and `summary` are optional but you should definitely use them. These properties help not only to properly describe the example in documentation. These properties make it easier to work with mocking and testing tools (like [microcks](https://microcks.io/)) so you can better identify what example should be used for mocking and what it does.

For more details check out [this pull request](https://github.com/asyncapi/spec/pull/534).

## New protocol bindings

The specification is now extended to support the following custom protocols through the bindings feature:
- `Mercure`, thanks to [Kévin Dunglas](https://github.com/dunglas). At the moment no specific bindings are necessary for this protocol For more details check out [this pull request](https://github.com/asyncapi/spec/pull/278) and [binding definition](https://github.com/asyncapi/bindings/tree/master/mercure).
- (TODO: not yet approved and merged)`IBM MQ`, thanks to [Dale Lane](https://github.com/dalelane) and [Richard Coppen](https://github.com/rcoppen). For more details check out [this pull request](https://github.com/asyncapi/spec/pull/537) and [binding definition](https://github.com/asyncapi/bindings/tree/master/ibmmq).
Add ibmmq once merged
- (TODO: not yet approved and merged) `AnypointMQ`
- `IBM MQ`, thanks to [Dale Lane](https://github.com/dalelane) and [Richard Coppen](https://github.com/rcoppen). For more details check out [this pull request](https://github.com/asyncapi/spec/pull/537) and [binding definition](https://github.com/asyncapi/bindings/tree/master/ibmmq).

## Custom schema formats mandatory vs recommended

Expand All @@ -39,4 +41,11 @@ Thanks to [Dale Lane](https://github.com/dalelane) you can now describe secured

We used and supported `defaultContentType` property to specify default content type to use when encoding/decoding a message's payload. [Lucas Block](https://github.com/BlockLucas) spotted that we do not have it defined in the specification. For more details check out [this pull request](https://github.com/asyncapi/spec/pull/419).

## Tooling support

The following tools are already updated to support 2.1.0 version of the specification:
- JSON Schema that supports validation of AsyncAPI documents is updated in [this](https://github.com/asyncapi/asyncapi-node) repository. Also `@asyncapi/specs` package has been updated on NPM to version 2.8.0 and it contains the 2.1.0 JSON Schema.
- [JavaScript Parser](https://github.com/asyncapi/parser-js/) uses latest `@asyncapi/specs` package and can be used to parse and validate `2.1.0` documents. Upgrade to 1.6.0 version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remember to change 1.6.0 version to the latest.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, will keep that one unresolved

- [AsyncAPI Generator](https://github.com/asyncapi/generator/) uses latest `@asyncapi/parser` package so while generating output, it is able to validate `2.1.0` documents. Upgrade to 1.8.0 version

> Photo by <a href="https://unsplash.com/@dougswinson?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Doug Swinson</a> on <a href="https://unsplash.com/s/photos/landing-eagle?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>