-
Notifications
You must be signed in to change notification settings - Fork 82
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
Mojo #687
Comments
Build artifacts committed to the repository: tomdasilva/Mojo#1 |
Hi ! invalid characters have been modified in the plugin.json file :) |
Thanks. Build artifacts are still an issue though. |
Hi ! I hope everything is fine now ... |
@tomdasilva |
Ok ! Is it fine now ? Thanks a lot :) |
One more thing: |
So many issues ;) i corrected it ! |
Your plugin has been integrated and will be available for all supported platforms with the next Plugin Manager update. Please let us know in this issue when a new version is available. We will reopen it. Thank you for providing your plugin to the Rack community. |
So great ! thanks lot ! |
Hi ! I updated my plugin.json file for the migration from v1 to v2 :) Have a good day |
Great job! Your plugin passed all integration tests and builds successfully against the current SDK However, we are not accepting submissions to the library for v2 of Rack yet. |
Update requested for |
Hi ! I made some major updates to my Plugin with three new modules. I wish to push them to the VCV library :) New version: v3.0 (https://github.com/tomdasilva/Mojo - updates were pushed to main branch) |
Manifest issues: tomdasilva/Mojo#5 |
Looks like @tomdasilva fixed this. |
Latest plugin revision crashes Rack when module browser loads. This is on GNU/Linux. @tomdasilva |
https://github.com/tomdasilva/Mojo
Hi !
I hope those three modules will be ok for getting into the VCV Library :)
Best Regards
Tom
The text was updated successfully, but these errors were encountered: