New ZLS binary location #141
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will keep the ZLS resources online until december, so there's enough time for everyone to update |
|
Thanks y'all. I'll close this PR and open future ones related to this topic as PRs into your branch Veikka :) (If there's anything to add, but tbh your branch looks good, I'll review it soon) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrating to our own infrastructure :)
Thanks for helping us for free all this time @masterq32 o7
This JSON index system also allows us to find the right Zig version based on some different parameters (what version of Zig ZLS was built with, the minimum required build version for the ZLS build runner, etc.), but that'll be implemented in a different PR. :)