-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Claiming namespace BarbossHack
#3461
Comments
@BarbossHack Granted! Nice hat BTW |
Thanks @kineticsquid 👍 I would like to remove/reupload my extension, to make it as "published by BarbossHack" Else, users would have to trust "alamin655" for the version v0.7.3, IMHO it's a security issue here... How could I do that please ? 🙏 |
Makes sense. Poof! |
Thanks 🚀 🙏 |
Hi @kineticsquid ! It seems that my extension is in an "unknown" state ... "extension not found" on https://open-vsx.org/extension/BarbossHack/crates-io In my open-vsx account, seems published, but no icon : In open-vsx search, cannot find it : In vscodium, cannot view it : Do I need to publish a v0.7.4 to publish again my extension ? |
@BarbossHack It looks like there was an issue with activating after it was published. Was this you publishing |
yeah one month ago i published 0.7.3 after you removed it. And it was working, but maybe it was some sort of cache from the previous publisher I'm ok for @tfroment to remove it, thank you ! |
ok, version 0.7.3 is removed now @BarbossHack @kineticsquid |
Seems ok now, thank you @tfroment @kineticsquid |
Hi there !
I'm here to claim my namespace
BarbossHack
, to be able to publish my VScode extension available here https://github.com/BarbossHack/crates-ioAs you can see, @alamin655 already published my extension here https://open-vsx.org/extension/BarbossHack/crates-io , but I don't know him and I would like to take the ownership of my namespace.
I point out that Alamin655 reached me so I can take the ownership of the namespace, so that my extension can be verified 👍
Thank you !
The text was updated successfully, but these errors were encountered: