openvsx
openvsx copied to clipboard
An open-source registry for VS Code extensions
Can we get additional information about publishers and activity through the `/admin` API. I'm looking for the most active publishers, number of extensions and number of versions/updates. Also, what are...
Hello, I am looking for a ways how to **implement allow listing of VS Code extensions**. Basically I would like to limit what extensions developers inside the organization can download...
I'm not sure if this relates to https://github.com/eclipse/openvsx/issues/450#issuecomment-1141948684 at all - i.e. the server not reflecting target at all. A quick look into the codebase would suggest it doesn't -...
When one goes to an extension page published by a user who isn't the verified publisher of a namespace, you get this scary warning message:  I like the...
Fixes #474 ### Testing Steps - Publish extension using privileged user: ``` curl --location --request POST 'http://localhost:8080/api/-/publish?token=super_token' \ --header 'Content-Type: application/octet-stream' \ --data-binary '@' ``` - JSON response `verified` field...
Following #484, it would be nice to let users know that an extension they are looking at is verified because it is published by a privileged user. I was thinking...
Use `extension.targetPlatform` instead of `options.target`. The logging format follows the same pattern as other parts of the codebase: https://github.com/eclipse/openvsx/blob/df28c16c4d919afaf1c8795ab0dfabd842ceb6e6/cli/src/get.ts#L106-L107 https://github.com/eclipse/openvsx/blob/df28c16c4d919afaf1c8795ab0dfabd842ceb6e6/server/src/main/java/org/eclipse/openvsx/ExtensionService.java#L190-L193 cc @radeksimko
Fixes #461 use allSettled in CLI, so that all publish processes finish Make publish retryable
we use ```shell npx ovsx publish ./filename.vsix -p *** ``` to publish. earlier it used to work correctly, from past one week, its taking for ever. fyi, it looks like...