-
Notifications
You must be signed in to change notification settings - Fork 204
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
Publish the new VS Code Extensions to Open VSX? #2882
Comments
@prestoncabe hello, I think we do not have official plan for this at this moment (at least I was not able to find such ticket), however in past we did it, see:
So I believe we could do it and your offer for the help will be much appreciated. I am not expert in the Open VSX registry, I think we just need to discuss details, for example the account used for uploading is something I am not sure about. @ederign @tiagobento you as very senior engineers were involved in this previously (I assume this from tickets and open vsx portal), would you mind to advise how to proceed? |
@jomarko Thanks for the swift reply, and I hope it's a relatively simple thing to do. I appreciate all the work y'all have been doing! 🥇 |
Hi @prestoncabe! Thanks for the interest on the Apache KIE VS Code Extensions 😊 Since the move to Apache we're trying to make things simpler, and publishing to Open VSX was something we decided not to do to expedite the release, but AFAIK we don't have any impediment preventing us from publishing there, it was just an optimization we did given the complexity of our releases already. Conversations about releasing 10.1 have already started, so I guess we can include that in the discussions for us to properly setup our credentials and publish it once the release is out. |
@tiagobento That all makes sense to me, thanks for responding and attending to this issue. ⭐ |
Hello, I just discovered the new "Apache KIE" prefixed extensions in the VS Code Marketplace. How exciting! I'm diving into using the new DMN editor right now.
Do you all have plans to publish the new extensions to the Open VSX Registry? The environments I typically work in are based on VS Code, but not VS Code itself so I rely on extensions being available at Open VSX.
I think I could technically do this myself(?), but I wanted to check to see if you all have plans for this already.
Happy to jump in and help make it happen if that's appropriate as well!
Thanks,
Preston
The text was updated successfully, but these errors were encountered: