You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it seems that users of this lsp have two options when installing/updating: cloning the repo and compiling from source, or cloning the repo and placing the corresponding binaries from github actions in the bin/<platform>/ folder. Would it be possible to remove the cloning step from this process entirely and either ship the required files alongside the binary in github actions or post releases on the github releases page with the corresponding version of the required files included?
This would make the installation/updating process significantly simpler as one can just download a zip, extract, and run. Thanks for considering.
The text was updated successfully, but these errors were encountered:
That is certainly possible in principle, but the issue is that there is no release workflow currently -- the binaries are purely a by-product of the CI testing.
I'm sure a PR adding such a release workflow would be appreciated!
Currently it seems that users of this lsp have two options when installing/updating: cloning the repo and compiling from source, or cloning the repo and placing the corresponding binaries from github actions in the
bin/<platform>/
folder. Would it be possible to remove the cloning step from this process entirely and either ship the required files alongside the binary in github actions or post releases on the github releases page with the corresponding version of the required files included?This would make the installation/updating process significantly simpler as one can just download a zip, extract, and run. Thanks for considering.
The text was updated successfully, but these errors were encountered: