Merge pull request #265 from asyncapi/release/2.0.0

Release 2.0.0
asyncapi · Sep 11, 2019 · b21cf1d · b21cf1d
2 parents ede0b8a + e4e0b57
commit b21cf1d
Show file tree

Hide file tree

Showing 17 changed files with 24 additions and 27 deletions.
diff --git a/README.md b/README.md
@@ -1,10 +1,7 @@
 <h1 align="center">
   <br>
-  <a href="https://asyncapi.org"><img src="./assets/logo.png" alt="AsyncAPI logo" width="200"></a>
-  <br>
-  AsyncAPI
-  <br>
-<h4 align="center">Create machine-readable definitions of your message-driven APIs</h4>
+  <a href="https://asyncapi.org"><img src="./assets/logo.png" alt="AsyncAPI logo" height="80"></a>
+<h4 align="center">Building the future of event-driven architectures</h4>
 <h6 align="center">We're on a mission to standardize message-based communication and increase interoperability of the different systems out there.</h6>
 <p align="center">
   <a href="#the-specification">Specification</a>
@@ -55,8 +52,8 @@
 
 ## The specification
 
-* [Version 2.0.0-beta](/versions/next/asyncapi.md) — [Machine-readable version](/versions/next/schema.json) 
-* [Version 1.2.0](/versions/1.2.0/asyncapi.md) — [Machine-readable version](/versions/1.2.0/schema.json) (latest stable)
+* [Version 2.0.0](/versions/next/asyncapi.md) — [Machine-readable version](/versions/2.0.0/schema.json) (latest stable) 
+* [Version 1.2.0](/versions/1.2.0/asyncapi.md) — [Machine-readable version](/versions/1.2.0/schema.json)
 * [Version 1.1.0](/versions/1.1.0/asyncapi.md) — [Machine-readable version](/versions/1.1.0/schema.json)
 * [Version 1.0.0](/versions/1.0.0/asyncapi.md) — [Machine-readable version](/versions/1.0.0/schema.json)
 

diff --git a/ROADMAP.md b/ROADMAP.md
@@ -30,8 +30,6 @@ This milestone is about improving developer/user experience for the specificatio
 
 This milestone is about figuring out how to map protocols to AsyncAPI documents.
 
-### Next milestones
-
 :arrow_right: [[v2.0.0] Augmentation](https://github.com/asyncapi/asyncapi/milestone/5) :white_check_mark: Current milestone
 
 This milestone is about creating mechanisms for the users to augment the AsyncAPI specification. We already have specification extensions, which provide a syntactical way to extend the spec. In this milestone, we should aim for providing the right mechanisms to extend the spec in different contexts and ways.
@@ -44,6 +42,8 @@ There's a new AsyncAPI version and now it's time for the tooling vendors to fini
 
 Official launch of AsyncAPI 2.0.0! Party hard! :beers:
 
+### Next milestones
+
 :arrow_right: [Backlog](https://github.com/asyncapi/asyncapi/projects/4)
 
 The purpose of the backlog is to temporarily group issues that may be considered for the future. Please, note that it doesn't mean they will get implemented, however, there is a big chance.
diff --git a/assets/logo.png b/assets/logo.png
diff --git a/examples/next/README.md → examples/2.0.0/README.md b/examples/next/README.md → examples/2.0.0/README.md
diff --git a/examples/next/anyof.yml → examples/2.0.0/anyof.yml b/examples/next/anyof.yml → examples/2.0.0/anyof.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: AnyOf example
   version: '1.0.0'

diff --git a/examples/next/application-headers.yml → examples/2.0.0/application-headers.yml b/examples/next/application-headers.yml → examples/2.0.0/application-headers.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: Application Headers example
   version: '1.0.0'

diff --git a/examples/next/correlation-id.yml → examples/2.0.0/correlation-id.yml b/examples/next/correlation-id.yml → examples/2.0.0/correlation-id.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: Correlation ID Example
   version: '1.0.0'

diff --git a/examples/next/gitter-streaming.yml → examples/2.0.0/gitter-streaming.yml b/examples/next/gitter-streaming.yml → examples/2.0.0/gitter-streaming.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 id: 'urn:com:gitter:streaming:api'
 info:
   title: Gitter Streaming API

diff --git a/examples/next/not.yml → examples/2.0.0/not.yml b/examples/next/not.yml → examples/2.0.0/not.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: Not example
   version: '1.0.0'

diff --git a/examples/next/oneof.yml → examples/2.0.0/oneof.yml b/examples/next/oneof.yml → examples/2.0.0/oneof.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: OneOf example
   version: '1.0.0'

diff --git a/examples/next/rpc-client.yml → examples/2.0.0/rpc-client.yml b/examples/next/rpc-client.yml → examples/2.0.0/rpc-client.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 id: 'urn:rpc:example:client'
 defaultContentType: application/json
 

diff --git a/examples/next/rpc-server.yml → examples/2.0.0/rpc-server.yml b/examples/next/rpc-server.yml → examples/2.0.0/rpc-server.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 id: 'urn:rpc:example:server'
 defaultContentType: application/json
 

diff --git a/examples/next/slack-rtm.yml → examples/2.0.0/slack-rtm.yml b/examples/next/slack-rtm.yml → examples/2.0.0/slack-rtm.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 id: 'urn:com:slack:rtm:api'
 info:
   title: Slack Real Time Messaging API
@@ -14,6 +14,9 @@ servers:
 
 channels:
   /:
+    publish:
+      message:
+        $ref: '#/components/messages/outgoingMessage'
     subscribe:
       message:
         oneOf:
@@ -63,9 +66,6 @@ channels:
           - $ref: '#/components/messages/manualPresenceChange'
           - $ref: '#/components/messages/memberJoinedChannel'
           - $ref: '#/components/messages/message'
-    subscribe:
-      message:
-        $ref: '#/components/messages/outgoingMessage'
 
 components:
   securitySchemes:

diff --git a/examples/next/streetlights.yml → examples/2.0.0/streetlights.yml b/examples/next/streetlights.yml → examples/2.0.0/streetlights.yml
@@ -1,4 +1,4 @@
-asyncapi: '2.0.0-rc2'
+asyncapi: '2.0.0'
 info:
   title: Streetlights API
   version: '1.0.0'

diff --git a/test/index.js b/test/index.js
@@ -1,4 +1,4 @@
-// Usage: npm test [-- --versions 1.2.0,next]
+// Usage: npm test [-- --versions 1.2.0,2.0.0]
 
 const util = require('util');
 const fs = require('fs');
@@ -71,7 +71,7 @@ const runForVersion = version => new Promise((resolve, reject) => {
 
 // RUNNING TESTS
 
-let versions = ['1.1.0', '1.2.0', 'next'];
+let versions = ['1.1.0', '1.2.0', '2.0.0'];
 
 if (process.argv.length > 2) {
   const args = process.argv.slice(2);

diff --git a/versions/next/asyncapi.md → versions/2.0.0/asyncapi.md b/versions/next/asyncapi.md → versions/2.0.0/asyncapi.md
@@ -4,7 +4,7 @@
 
 Part of this content has been taken from the great work done by the folks at the [OpenAPI Initiative](https://openapis.org). Mainly because **it's a great work** and we want to keep as much compatibility as possible with the [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification).
 
-#### Version 2.0.0-rc2
+#### Version 2.0.0
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
 

diff --git a/versions/next/schema.json → versions/2.0.0/schema.json b/versions/next/schema.json → versions/2.0.0/schema.json
@@ -1,5 +1,5 @@
 {
-  "title": "AsyncAPI 2.0.0-rc2 schema.",
+  "title": "AsyncAPI 2.0.0 schema.",
   "$schema": "http://json-schema.org/draft-07/schema#",
   "type": "object",
   "required": [
@@ -17,7 +17,7 @@
     "asyncapi": {
       "type": "string",
       "enum": [
-        "2.0.0-rc2"
+        "2.0.0"
       ],
       "description": "The AsyncAPI specification version of this document."
     },