Aart van Baren

@kineticsquid Ok, let's schedule a demo

Hi @marcdumais-work, I think you want to use the `--pre-release`[[1](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions)] flag for `next` versions. It used to be that `preview`[[2](https://devblogs.microsoft.com/visualstudio/new-preview-label-for-visual-studio-extensions-2/)] had the functionality of `pre-release`, but now these flags work...

Hi @pm4rcin, the API supports platform-specific releases for a while now. I think the issue can be closed. @radeksimko Please re-open this issue if platform specific releases still don't work...

@kineticsquid I can't help you with DB data related issues. You should ask the Eclipse helpdesk.

> Or will they need to run some queries to determine the state of the tables? Yes.

@kineticsquid No, not that I'm aware of. Furthermore there's a case-insensitive unique constraint on the namespace name, so this isn't possible on the database level.

When I go to https://open-vsx.org/namespace/stateful it works instead of getting an error as mentioned in https://github.com/eclipse/openvsx/issues/731#issuecomment-1554727546. When I query for stateful https://open-vsx.org/api/-/query?namespaceName=stateful, I don't get any duplicates (please note that...

@kineticsquid No, go ahead. Just keep in mind that delete operations run async, so you can't re-publish right away.

@sourishkrout The @eclipsewebmaster ran the select queries against the production database and everything looks fine. It looks like [V1_39__Fix_Unique_Constraints.sql](https://github.com/eclipse/openvsx/blob/master/server/src/main/resources/db/migration/V1_39__Fix_Unique_Constraints.sql) cleaned it up. Can you try to publish an extension to...

> This process should be that we first remove the extension from the registry, then update the list, meaining that the malicious list entries won't be of any use to...