Merge branch 'master' into Dule-asyncAPI

.all-contributorsrc

@@ -254,6 +254,15 @@
  "contributions": [
  "doc"
  ]
+ },
+ {
+ "login": "Harish-b-03",
+ "name": "Harish",
+ "avatar_url": "https://avatars.githubusercontent.com/u/69810789?v=4",
+ "profile": "https:/Harish-b-03",
+ "contributions": [
+ "code"
+ ]
  }
  ],
  "contributorsPerLine": 7,

.github/workflows/automerge-orphans.yml

@@ -9,6 +9,7 @@ on:
 
 jobs:
  identify-orphans:
+ if: startsWith(github.repository, 'asyncapi/')
  name: Find orphans and notify
  runs-on: ubuntu-latest
  steps:

.github/workflows/autoupdate.yml

@@ -20,6 +20,7 @@ on:
 
 jobs:
  autoupdate-for-bot:
+ if: startsWith(github.repository, 'asyncapi/')
  name: Autoupdate autoapproved PR created in the upstream
  runs-on: ubuntu-latest
  steps:

.github/workflows/help-command.yml

@@ -25,7 +25,7 @@ jobs:
 
  - `/ready-to-merge` or `/rtm` - This comment will trigger automerge of PR in case all required checks are green, approvals in place and do-not-merge label is not added
  - `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
- - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict.
+ - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict or it is a draft PR.
  create_help_comment_issue:
  if: ${{ !github.event.issue.pull_request && contains(github.event.comment.body, '/help') && github.actor != 'asyncapi-bot' }}
  runs-on: ubuntu-latest

.github/workflows/if-nodejs-release.yml

@@ -48,6 +48,15 @@ jobs:
  - if: steps.packagejson.outputs.exists == 'true'
  name: Run test
  run: npm test
+ - if: failure() # Only, on failure, send a message on the 94_bot-failing-ci slack channel
+ name: Report workflow run status to Slack
+ uses: 8398a7/action-slack@v3
+ with:
+ status: ${{ job.status }}
+ fields: repo,action,workflow
+ text: 'Release workflow failed in testing job'
+ env:
+ SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}
 
  release:
  needs: [test-nodejs]
@@ -84,3 +93,12 @@ jobs:
  GIT_COMMITTER_NAME: asyncapi-bot
  GIT_COMMITTER_EMAIL: [email protected]
  run: npm run release
+ - if: failure() # Only, on failure, send a message on the 94_bot-failing-ci slack channel
+ name: Report workflow run status to Slack
+ uses: 8398a7/action-slack@v3
+ with:
+ status: ${{ job.status }}
+ fields: repo,action,workflow
+ text: 'Release workflow failed in release job'
+ env:
+ SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}

.github/workflows/if-nodejs-version-bump.yml

@@ -24,6 +24,13 @@ jobs:
  - name: Check if Node.js project and has package.json
  id: packagejson
  run: test -e ./package.json && echo "::set-output name=exists::true" || echo "::set-output name=exists::false"
+ - if: steps.packagejson.outputs.exists == 'true'
+ name: Setup Node.js
+ uses: actions/setup-node@v2
+ with:
+ node-version: 14
+ cache: 'npm'
+ cache-dependency-path: '**/package-lock.json'
  - if: steps.packagejson.outputs.exists == 'true'
  name: Install dependencies
  run: npm install
@@ -46,4 +53,13 @@ jobs:
  author: asyncapi-bot <[email protected]>
  title: 'chore(release): ${{github.event.release.tag_name}}'
  body: 'Version bump in package.json for release [${{github.event.release.tag_name}}](${{github.event.release.html_url}})'
- branch: version-bump/${{github.event.release.tag_name}} 
+ branch: version-bump/${{github.event.release.tag_name}}
+ - if: failure() # Only, on failure, send a message on the 94_bot-failing-ci slack channel
+ name: Report workflow run status to Slack
+ uses: 8398a7/action-slack@v3
+ with:
+ status: ${{ job.status }}
+ fields: repo,action,workflow
+ text: 'Unable to bump the version in package.json after the release'
+ env:
+ SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}

.github/workflows/link-check-cron.yml

@@ -11,6 +11,7 @@ on:
 
 jobs:
  External-link-validation-weekly:
+ if: startsWith(github.repository, 'asyncapi/')
  runs-on: ubuntu-latest
  steps:
  - uses: actions/checkout@v3
@@ -33,4 +34,4 @@ jobs:
  fields: repo,action,workflow
  env:
  SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}
- if: failure() # Only, on failure, send a message on the Slack Docs Channel (if there are broken links)
+ if: failure() # Only, on failure, send a message on the 94_bot-failing-ci slack channel

.github/workflows/stale-issues-prs.yml

@@ -9,6 +9,7 @@ on:
 
 jobs:
  stale:
+ if: startsWith(github.repository, 'asyncapi/')
  name: Mark issue or PR as stale
  runs-on: ubuntu-latest
  steps:

README.md

@@ -2,7 +2,7 @@
 
 ---
 <!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
-[![All Contributors](https://img.shields.io/badge/all_contributors-22-orange.svg?style=flat-square)](#contributors-)
+[![All Contributors](https://img.shields.io/badge/all_contributors-24-orange.svg?style=flat-square)](#contributors-)
 <!-- ALL-CONTRIBUTORS-BADGE:END -->
 [![Netlify Status](https://api.netlify.com/api/v1/badges/b2137407-b765-46c4-95b5-a72d9b1592ab/deploy-status)](https://app.netlify.com/sites/asyncapi-website/deploys)
 
@@ -65,6 +65,14 @@ npm run build
 
 Generated files of the website go to the `.next` folder.
 
+## JSON Schema definitions
+
+All AsyncAPI JSON Schema definition files are being served within the `/definitions/<file>` path. The content is being served from GH, in particular from https:/asyncapi/spec-json-schemas/tree/master/schemas.
+This is possible thanks to the following:
+
+1. A [Netlify Rewrite rule](https://docs.netlify.com/routing/redirects/rewrites-proxies/) located in the [netlify.toml](netlify.toml) file, which acts as proxy for all requests to the `/definitions/<file>` path, serving the content from GH without having an HTTP redirect.
+2. A [Netlify Edge Function](https://docs.netlify.com/netlify-labs/experimental-features/edge-functions/) that modifies the `Content-Type` header of the rewrite response to become `application/schema+json`. This lets tooling, such as [Hyperjump](https://json-schema.hyperjump.io), to fetch the schemas directly from their URL.
+
 ## Project structure
 
 This repository has the following structure:
@@ -85,6 +93,8 @@ This repository has the following structure:
  ├── public # Data for site metadata and static blog such as images
  ├── scripts # Scripts used in the build and dev processes
  ├── next.config.js # Next.js configuration file
+ ├── netlify # Code that runs on Netlify
+ │ ├── edge-functions # Netlify Edge-Functions code
  ├── postcss.config.js # PostCSS configuration file
  └── tailwind.config.js # TailwindCSS configuration file
 ```
@@ -127,6 +137,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
  <tr>
  <td align="center"><a href="http://juanarce.me"><img src="https://avatars.githubusercontent.com/u/30204147?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Juan A.</b></sub></a><br /><a href="https:/asyncapi/website/commits?author=jaas666" title="Code">💻</a></td>
  <td align="center"><a href="https:/luphieanza"><img src="https://avatars.githubusercontent.com/u/20577131?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Muhammad Rafly Andrianza</b></sub></a><br /><a href="https:/asyncapi/website/commits?author=luphieanza" title="Documentation">📖</a></td>
+ <td align="center"><a href="https:/Harish-b-03"><img src="https://avatars.githubusercontent.com/u/69810789?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Harish</b></sub></a><br /><a href="https:/asyncapi/website/commits?author=Harish-b-03" title="Code">💻</a></td>
  </tr>
 </table>