-
Notifications
You must be signed in to change notification settings - Fork 79
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
Nix lockFileMaintenance
is broken
#713
Comments
looks like something on nix side has changed. 🤔 how does nix detect it's home dir? @JamieMagee can you help? |
@rarkins renovate should not pass |
@budimanjojo how are you running renovate? (GitHub action, helm chart, docker cli ...) please be as detailed as possible |
Sorry, I'm using GHA (mentioned above actually :)). Here's the workflow file: https://github.com/budimanjojo/dotfiles/blob/master/.github/workflows/renovate.yaml |
moved the issue, as it's probably the docker user change here |
@viceice thanks for investigating. This appears to be a breaking change in nix |
should we lock nix to a lower version inside renovate for now? |
@budimanjojo You can workaround with renovate {
"constraints": {
"nix": "< 2.14.0"
}
} Footnotes |
Thanks! |
Yeah, the version of |
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
No response
If you're self-hosting Renovate, select which platform you are using.
github.com
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
Describe the bug
I'm using GitHub Action to run Renovate, it's been 2 weeks that I haven't got a
flake.lock
PR fromrenovate
so I decided to take a look. Seems like there's a problem with thebuildpack
docker container. Below is the relevant log that I suspect is causing the problem.Relevant debug logs
Have you created a minimal reproduction repository?
I have read the minimal reproductions documentation and linked to such a repository in the bug description
The text was updated successfully, but these errors were encountered: