fix: add missing security schemes to correlation id example #515
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
@195858 thanks a lot, can you update your branch please |
…epo (#510) * chore: remove everything that is not related to the spec * fix wording on sponsors * Get review documents back
|
Kudos, SonarCloud Quality Gate passed!
|
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
|
|
It is actually not included in the release. This was an unintentional release caused by the release automation initial run. 1.0 version of the spec was released a long time ago. The release mentioned by the bot was removed. |
|
🎉 This PR is included in version 2.1.0-2021-06-release.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
Not included in release 2.1 yet, 2.1 was mistakenly triggered by our automation. |
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Fixes #509 - as per suggestion copied in security schema element from lighting API example.
Verified spec is valid using the AsynAPI playground online.