chore(deps): lock file maintenance #875

Open

renovate wants to merge 1 commit from renovate/lock-file-maintenance into main

pull from: renovate/lock-file-maintenance

merge into: jalil:main

jalil:main

jalil:release-plz-2026-02-15T23-07-30Z

jalil:jalil/allow-unix-sockets

jalil:release-plz-2025-11-10T21-06-59Z

jalil:push-yzyrkwyqprvk

jalil:release-plz-2025-08-29T15-04-46Z

Conversation 1 Commits 1 Files changed 2 +29 -29

renovate commented 2026-07-13 00:01:47 +02:00

Collaborator

Copy link

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: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

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**: (UTC) - Branch creation - Between 12:00 AM and 03:59 AM, only on Monday (`* 0-3 * * 1`) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNTAuMSIsInVwZGF0ZWRJblZlciI6IjQzLjE1MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

renovate added 1 commit 2026-07-13 00:01:47 +02:00

chore(deps): lock file maintenance 45b2d8a54d

renovate scheduled this pull request to auto merge when all checks succeed 2026-07-13 00:01:47 +02:00

forgejo-actions commented 2026-07-13 00:09:13 +02:00

Copy link

Flake output sizes

Definitions

• Name: the name of the package/configuration.
• Size: the closure size (size on disk/NAR size + all transitive dependencies).
• NAR Size: the size of the build output (package without the dependencies).
• [NAR] Size Change: the amount changed compared to the main branch.

Tips on reading this data

• For NixOS/Home-Manager configurations you generally care only about the Size (closure size/size on disk).
  • Reduce the Size by disabling unneeded services/default packages.
• For Packages you care about both the Size and the NAR Size.
  • Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
  • Reduce the Size by reducing the dependencies (e.g. buildInputs).
  • Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

Packages

Name	Size	Size Change	NAR Size	NAR Size Change
default	49MiB	49MiB	2.1MiB	2.1MiB
release-script	417MiB	417MiB	752B	752B
webnsupdate	48MiB	-20KiB	2.0MiB	-20KiB

<!-- AUTOGENERATED by nix-flake-outputs-size action --> ## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS/Home-Manager configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 49MiB | 49MiB | 2.1MiB | 2.1MiB | | `release-script` | 417MiB | 417MiB | 752B | 752B | | `webnsupdate` | 48MiB | -20KiB | 2.0MiB | -20KiB |

jalil was assigned by renovate 2026-07-13 00:11:09 +02:00

renovate force-pushed renovate/lock-file-maintenance from 45b2d8a54d to e1210b33f8 2026-07-14 15:51:13 +02:00 Compare

Some checks failed

Hide all checks

/ build (pull_request) Successful in 4m14s

Required

Details

/ checks (x86_64-linux, clippy) (pull_request) Failing after 38s

Required

Details

/ checks (x86_64-linux, deny) (pull_request) Successful in 27s

Required

Details

/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 1m40s

Required

Details

/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 1m43s

Required

Details

/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 1m4s

Required

Details

/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 1m7s

Required

Details

/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 1m9s

Required

Details

/ checks (x86_64-linux, treefmt) (pull_request) Successful in 6s

Required

Details

/ checks (x86_64-linux, nextest) (pull_request) Successful in 1m15s

Required

Details

/ trigger-release (pull_request) Has been skipped

Required

Details

/ report-size (pull_request) Successful in 25s

Required

Details

Some required checks were not successful.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/lock-file-maintenance:renovate/lock-file-maintenance

git switch renovate/lock-file-maintenance

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

chore

Cleanup/trivial updates

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

release

A PR created by `release-plz`

  

wontfix

This won't be fixed

No labels

bug

chore

duplicate

enhancement

help wanted

invalid

question

release

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

jalil

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jalil/webnsupdate!875

No description provided.