Skip to content
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

Studio started with AsyncAPI cli tools does not support version 3.0 #1085

Closed
lovebug356 opened this issue Jan 23, 2024 · 3 comments · Fixed by #1086
Closed

Studio started with AsyncAPI cli tools does not support version 3.0 #1085

lovebug356 opened this issue Jan 23, 2024 · 3 comments · Fixed by #1086
Labels
bug Something isn't working released

Comments

@lovebug356
Copy link
Contributor

When starting the AsyncAPI Studio from the cli tools. The instance complains on not supporting specification 3.0

Can be reproduced with creating a new file with the CLI tools and auto starting Studio:

asyncapi new file
? name of the file? asyncapi.yaml
? open in Studio? Yes
Created file asyncapi.yaml...
Studio is running at http://localhost:3210?liveServer=3210
Watching changes on file asyncapi.yaml
image

Tested with:

$ asyncapi --version
@asyncapi/cli/1.3.3 darwin-arm64 node-v20.7.0
@lovebug356 lovebug356 added the bug Something isn't working label Jan 23, 2024
Copy link
Member

derberg commented Jan 23, 2024

@asyncapi/studio dependency must be updated to latest version as it uses old 0.17 -> https:/asyncapi/cli/blob/master/package.json#L22

@KhudaDad414 did you plan to bump? automated bump do not work as you did some monorepo stuff in studio repo so I bet standard autobump workflow do not work as expected anymore

@DavidSchmidt00
Copy link

They are already working on it, see #629

@asyncapi-bot
Copy link
Contributor

🎉 This issue has been resolved in version 1.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants