-
Notifications
You must be signed in to change notification settings - Fork 30
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
Consider nix installer being explicit #6
Comments
What do you think about adding an I added the |
That makes sense, but it's surprising/out of control for those that don't maintain this action :) I'd expect the install action to always default to the latest Nix (starting with Nix 2.4 rc1). As soon as that changes to a bugfix release you might need internally, that's unexpected for me as a downstream user. Thanks for explaining the motivation! |
Definitely fair. Is |
It is, sorry for the confusion (pre-rc1 is a weird naming). |
Just an update (in case you didn't see the linked PR) -- it doesn't look like there's any way to have a conditional step in a composite action. I've filed a ticket with GitHub support to see if there's a reason for this, or if there's any chance they will support the I'll keep this issue posted on further updates. |
If we don't hear back from GitHub by Wednesday we're going to go ahead and cut the install step out in a v3 release. |
So, GitHub support got back to me, and there are currently no plans to support the |
I just cut v3. Thanks for your feedback :) |
Installer action comes with nix.conf options, different installers, etc.
One way would be to expose those via this action, but then what's the point of doing that? :)
The text was updated successfully, but these errors were encountered: