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
Hi friends, thanks for building this language server!
Context and reach
As most zig developers, my workflow is almost always on the bleeding edge of the newest releases. I often take one day every two weeks to update all projects at once to the latest releases. Including zls. But since it is impossible to do all updates at once, I work with devcontainers to have granular versions per project.
The solution works perfectly when there are no breaking changes between the zig version of the container and zls, but when there is (and this happens a lot) I can only download the latest build for zls, which usually only works with the latest zig, and that may not be the case for all of my projects.
Solution space exploration
Since builds are being built and uploaded using a specific zig version, I was thinking that maybe there can be one extra alias/indirection/redirection to download older versions by zig version. In that case, I would be able to change my scripts like this:
@SuperAuguste did some great work on our CI and we can now provide download URLs to non-master builds.
All metadata is about builds in collected into a single index.json which should hopefully provide you with the necessary information.
download URLs would resolve like this: https://zigtools-releases.nyc3.digitaloceanspaces.com/zls/<ZLS version>/<target>/zls[.exe]
example: https://zigtools-releases.nyc3.digitaloceanspaces.com/zls/0.12.0-dev.111+ebbae55/x86_64-linux/zls
Hi friends, thanks for building this language server!
Context and reach
As most zig developers, my workflow is almost always on the bleeding edge of the newest releases. I often take one day every two weeks to update all projects at once to the latest releases. Including zls. But since it is impossible to do all updates at once, I work with devcontainers to have granular versions per project.
The solution works perfectly when there are no breaking changes between the zig version of the container and zls, but when there is (and this happens a lot) I can only download the latest build for zls, which usually only works with the latest zig, and that may not be the case for all of my projects.
Solution space exploration
The text was updated successfully, but these errors were encountered: