Skip to content

Push tags for vscode extension versions #5509

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

Closed
mattburgess opened this issue Jul 23, 2020 · 2 comments
Closed

Push tags for vscode extension versions #5509

mattburgess opened this issue Jul 23, 2020 · 2 comments

Comments

@mattburgess
Copy link

I use VSCodium, which since v1.46.0 doesn't use the Microsoft Marketplace for extensions, but instead uses https://open-vsx.org/.
The rust-analyzer extension is being published to that MarketPlace by the code at https://github.com/open-vsx/publish-extensions/blob/1542b6ec2a98eb5fc153995866888744b5557b12/extensions.json#L486-L491.

It would be nice if rust-analyzer/rust-analyzer would publish tags with the same version number as the extension is published with to the MS Marketplace. That way, a simple PR to the open-vsx repo above will have the same version made available there as well.

At the moment, openvsx has a 0.4.0-dev version available which doesn't correspond to any upstream versioning scheme at all. That makes it really unclear as to how recent it is, what features it should have, etc.

@jonas-schievink
Copy link
Contributor

The plan is to use https://github.com/rust-lang/vscode-rust/ instead of the extension in this repo, so maybe ask there?

@mattburgess
Copy link
Author

Ah, that's great. And it turns out they already push tags and version numbers correctly, such that https://open-vsx.org/extension/rust-lang/rust is already there. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants