Claiming namespace file-icons

[Alhadis]

Hello,

I'm the author and maintainer of the @file-icons project, including an extension for VS Code (Marketplace | Repository). In file‑icons/vscode#70, two users encouraged me to make an official release on open-vsx.org, which is what I'm doing now.

Note that there appears to be a duplicate (and outdated) version of this package on open-vsx.org, published by one @enriquecaballero with the ID fileicons.file-icons. The correct version of the package (and the one I'm claiming ownership of) is file-icons.file-icons.

/cc @jwaggy, @Lewatoto

[enriquecaballero]

Alright, even better. How can I unpublish?

[Alhadis]

How can I unpublish?

I'm not sure. Hopefully somebody here can answer that question for us. 😅

[kineticsquid]

@enriquecaballero Thanks!

@Alhadis Fortunately, I have that super power. I've un-published 1 version of fileicons.file-icons. Currently namespace file-icons has one member, @appelgriebsch. I am making you owner. I'll note that your extension is currently auto-published. See extensions.json. You can leave this, or submit a PR to remove the lines which will leaving publishing in your hands.

[Alhadis]

I'll note that your extension is currently auto-published.

That means I only need to publish updates to VSCode's Marketplace, right? And open-vsx.org will mirror new releases automatically? Because that'd be grouse. 😁 (Also, I'll remove @appelgriebsch, since he's a total stranger…)

[kineticsquid]

Yep, makes sense to remove @appelgriebsch. And yes, when the auto-publishing job runs (I think it's nightly) if you've updated your extension in the Visual Studio Marketplace, we'll update as well. I can see you're 1.1.0 in both registries with both updates happening about 2 weeks ago.