-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
feat: removing v3 check for bundle command #1138
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is feat
as it is new feature
but also think you need update tests to make sure they run against v3, as we care the most about the latest version. Of course if you think we can still have separate test for v2.
this was an unfortunate asyncapi/cli limitation to run into after converting my spec from 2.6.0 -> 3.0.0. is there anything I can assist with to help land this feature soon? or are we just waiting on the maintainer code review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Quality Gate passedIssues Measures |
/rtm |
🎉 This PR is included in version 1.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
V3 check was put on all commands in CLI to prevent compiling v3 spec if the tool didn't support it yet. Since bundler now supports spec V3 this PR is removing that check from the CLI.
Related issue(s)
Fixes #1137