fix: security schemas by upgrading the dependency #1086
Conversation
🦋 Changeset detectedLatest commit: be9a235 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![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 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.
✅ Deploy Preview for studio-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for modest-rosalind-098b67 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for asyncapi-studio-design-system ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
RobinTail
changed the title
RobinTail
force-pushed
the
issue-1066-security-refs
branch
from
d1af2dd to
6b86367
Compare
|
RobinTail
requested review from
magicmatatjahu,
KhudaDad414,
Amzani and
asyncapi-bot-eve
as code owners
RobinTail
changed the title
RobinTail
changed the title
|
@Amzani , please review. |
|
/rtm |
|
Thanks for the contribution @RobinTail 🙇 |
Description
@asyncapi/react-componentpackage): Incorrect rendering of security schemas: by reference and inline asyncapi-react#993Related issue(s)
Fixes #1066