Skip to content

Lock file maintenance #722

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

Merged
merged 1 commit into from
Jun 13, 2025
Merged

Lock file maintenance #722

merged 1 commit into from
Jun 13, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 9, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@Mic92 Mic92 force-pushed the renovate/lock-file-maintenance branch from 41a626c to 1db2ab1 Compare June 13, 2025 09:38
@Mic92 Mic92 enabled auto-merge June 13, 2025 09:38
@Mic92 Mic92 added this pull request to the merge queue Jun 13, 2025
Merged via the queue into main with commit 4a356e3 Jun 13, 2025
15 checks passed
@Mic92 Mic92 deleted the renovate/lock-file-maintenance branch June 13, 2025 09:47
@vcunat
Copy link
Member

vcunat commented Jun 13, 2025

Honestly, I'm not sure why we're even locking. People don't redeploy everything on these merge requests, right? In that case you don't really have an idea which lockfile got deployed to which machine or whether the committed lockfile ever truly worked. Am I just confused?

@mweinelt
Copy link
Member

When I merge a nixpkgs lock bump I tend to deploy it as well.

@jfly
Copy link
Contributor

jfly commented Jun 13, 2025

That doesn't feel like an an argument against a lockfile, it feels like an argument that we're missing some tooling: either CD (continuous deployment), and/or tracking which infra commit was deployed on each machine at a given time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants