Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions renovate.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we be generating this file with filegen, so all projects get renovate config by default?

"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended",
"schedule:daily",
"schedule:automergeDaily"
],
Comment thread
cursor[bot] marked this conversation as resolved.
"timezone": "Europe/Vienna",
"enabledManagers": [
"nix"
],
"nix": {
"enabled": true
},
"lockFileMaintenance": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's pretty common for flake inputs to change their inputs, causing .follows to get out of sync. We should add a flake-edit follow to our prek hooks to ensure this doesn't cause problems.

"enabled": true,
"schedule": "before 4am"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renovate skips required filegen step

Medium Severity

The new Renovate setup updates flake.lock (and possibly flake.nix) but does not run nix run .#filegen-activate, which the README documents as mandatory after dependency updates. CI runs the filegen pre-commit hook via prek, so PRs that change flake inputs without refreshing generated .github/workflows and .pre-commit-config.yaml can fail even when the lock bump itself is valid.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 7e28abb. Configure here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've put some care into not having nix store paths in the generated files any more, so this should only really be a problem for downstream repositories when ES changes the filegen output intentionally.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes to flake inputs might also introduce changes to e.g. treefmt.toml. This risks devshell components not being compatible with their configuration files.

It's a small risk, but worth considering.