-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
upgrade parser to version 3(next-major) #409
Comments
@KhudaDad414 I would like to take on this issue. |
hello @KhudaDad414 the latest version (v2.0.0-next-major.15) of @asynapi/parser-js is in pre-release, how do you recommend I go about this. |
@oviecodes by changing the current version to |
@KhudaDad414 I've opened an issue on the |
Hey @KhudaDad414 I would like to take this issue. |
@ConnectBhawna that's great. @oviecodes do you plan to continue the work or should it be assigned to @ConnectBhawna? |
@KhudaDad414 please assign it to @ConnectBhawna , thanks. |
@ConnectBhawna, let me know if there was anything that I could help with. :) |
/progress 10 |
/progress 40 |
/progress 50 |
/progress 90 |
🎉 This issue has been resolved in version 0.27.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Reason/Context
Following a recent discussion with @Souvikns and @fmvilas it seems like it's a plausible idea to use the latest version (v3.0.0-next-major.5) of @asynapi/parser-js in Glee.
Why?
Scope
The text was updated successfully, but these errors were encountered: