-
Notifications
You must be signed in to change notification settings - Fork 56
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
Update to unstable version by default instead of stable version #198
Comments
Currently we use the atom feed to not have to have github api tokens. You can filter however using regexes like this:
|
Semver is something that is hard to rely on since projects in general seem not to follow it consistently. |
You can also put this in your package definition like this:
And than do |
Got that, thanks for the explanation! |
Hello!
I find out that for some tags
nix-update
try to update a package to unstable version (by semver) by default.For example for ethereum.nix project it tries to update lighthouse from
4.5.0
to4.5.222-exp
The text was updated successfully, but these errors were encountered: