-
Notifications
You must be signed in to change notification settings - Fork 265
matklad.rust-analyzer is out of date #342
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
Comments
Salut Simon ! 👋 😁
Whoops, good catch. These updates are indeed automated, but it looks like the automation started failing 2-3 weeks ago: https://github.com/open-vsx/publish-extensions/actions/workflows/upgrade-extensions.yml Will investigate & fix. On a side note, this may be a good time to re-consider publishing to OpenVSX from the The fix is actually as easy as adding a single at the bottom of .github/workflows/release.yaml. The line is:
|
Update: Fixed in https://github.com/open-vsx/publish-extensions/pull/343/files Latest Thanks for reporting the broken auto-upgrades! |
Thanks for the quick fix! I see that #342 is submitted from your personal account (rather than some bot account). Does it mean you make PRs like this manually? |
You're very welcome! 🙌
So,
|
https://open-vsx.org/extension/matklad/rust-analyzer currently lists version 0.2.563 as "latest", whereas https://marketplace.visualstudio.com/items?itemName=matklad.rust-analyzer has version 0.2.591.
It looks like the last update was made by @jankeromnes in #333. Are such updates automated? Is making a new one blocked on something?
For context, I reported a bug rust-lang/rust-analyzer#8792 upstream and only when investigating that did I realize that the Archlinux build of Code OSS uses open-vsx.org instead of Microsoft’s Marketplace.
rust-analyzer’s development is rather active these days, so it can be misleading to have Code OSS say "All extensions are up to date" when in fact an old, buggy version is being used. If automating updates turns out difficult it might be better to not have this extension on open-vsx at all rather than have an old version that claims to be the latest.
The text was updated successfully, but these errors were encountered: