-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Include nightly versions #4
Comments
When I run the same command ( |
I like being able to easily install the latest nightly build version with I think it would still be useful to have individual nightly build versions installable with asdf. For some additional context, the recommended way to use zig (aside from evaluation) is to use a nightly build. Since nightly builds can change a lot, and some can have major problems, it makes sense to be able to pin specific nightly build versions for different projects. I'm currently doing this with vendoring, but I'd much rather use asdf and One potential issue is that adding nightly build versions to this plugin would result in a long version list after a while, since there will be one for each day. I'm not sure how much of a problem this could become, depending on when zig starts using a better release process. Additional thoughts? Are you open to a pull request? |
|
Pardon my confusion in assuming you were the repo owner. Also good callout on what repo |
yeah i wish "master": { // << what you need to install
"version": "0.11.0-dev.2546+cb54e9a3c", // << what you get Source:
We have a HTTP server now 🥳 https://ziglang.org/documentation/master/std/#A;std:http.Server |
Any luck with this thread? |
The Bash script retrieves https://ziglang.org/download/index.json, which lists the current v11.0-dev.* nightly versions. However, when I run
asdf list all zig
I only see the stable versions (0.1.1 through 0.10.1).Could this be changed to also include nightly versions?
Unfortunately, I can't really tell where in the script the filtering happens, otherwise I'd change it myself.
The text was updated successfully, but these errors were encountered: