openvsx
openvsx copied to clipboard
eclipse
An open-source registry for VS Code extensions
It would be really helpful to have a simple helm chart to deploy this project.
This commit moves `ovsx.js` to the root of the package. This way we don't need to copy the file from `src` to `lib` at build time.
Also check mirror mode publish token clean up.
See https://github.com/EclipseFdn/open-vsx.org/issues/2100.
As described in https://github.com/open-vsx/publish-extensions/issues/689, there is something wrong with how we detect licenses. If you take GitLens and publish it at its latest version (`14.0.1`), the MIT License gets displayed...
We're using a script to mirror extensions from open-vsx.org to our internal registry. It compares what's already present there to what we're requesting, and only mirrors the extension if it's...
I am trying to publish an update to [`googlecloudtools.cloudcode`](https://open-vsx.org/extension/googlecloudtools/cloudcode). I uploaded version 1.22.0 3 days ago. According to the settings page it was published: 
Fixes #587 Add optional access token to RegistryAPI Add API documentation
Update ElasticSearch to 8.7.1 in documentation
The attempt to publish a platform-specific extension that previously was uploaded to MSFT's marketplace without errors. The vsix files are available here https://github.com/stateful/vscode-runme/releases/tag/1.1.1 ``` npx ovsx publish --debug --packagePath runme-darwin-arm64-1.1.1.vsix...
