jalil/configuration.nix
1
1
Fork 0
Code Issues 2 Pull requests 1 Projects Activity Actions

chore(deps): lock file maintenance #234

Merged
renovate merged 1 commit from renovate/lock-file-maintenance into main 2025-01-08 01:34:37 +01:00
Conversation 2 Commits 1 Files changed 3 +13 -13
renovate commented 2025-01-08 00:50:49 +01: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: Branch creation - "* 0-1 * * " (UTC), Automerge - " 1-2 * * *" (UTC).

🚦 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 Renovate Bot.

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 - "* 0-1 * * *" (UTC), Automerge - "* 1-2 * * *" (UTC). 🚦 **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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMDUuMiIsInVwZGF0ZWRJblZlciI6IjM4LjEwNS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate added 1 commit 2025-01-08 00:50:49 +01:00
chore(deps): lock file maintenance
All checks were successful
/ check (nvimDev) (push) Successful in 5s
Details
/ check (nvimHeadless) (push) Successful in 2s
Details
/ check (nvimNoBundledBins) (push) Successful in 4s
Details
/ check (nvimNoLsp) (push) Successful in 4s
Details
/ check (nvimNoTSGrammars) (push) Successful in 5s
Details
/ check (treefmt) (push) Successful in 3s
Details
/ build (audiomenu) (push) Successful in 43s
Details
/ build (docs) (push) Successful in 3s
Details
/ build (jpassmenu) (push) Successful in 56s
Details
/ build (nixosConfigurations.vm.config.system.build.toplevel) (push) Successful in 33s
Details
/ build (nvim) (push) Successful in 9s
Details
/ report-size (push) Successful in 1m5s
Details
b1b3ff03e6
renovate scheduled this pull request to auto merge when all checks succeed 2025-01-08 00:50:49 +01:00
forgejo-actions commented 2025-01-08 01:14:09 +01:00
First-time contributor
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 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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change
vm 10GiB 12MiB 19KiB 0B

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 0B 1.4MiB 0B
docs 2.4MiB 0B 2.4MiB 0B
docs-home-markdown 11KiB 0B 11KiB 0B
docs-nixos-markdown 6.3KiB 0B 6.3KiB 0B
docs-nvim-markdown 1.9KiB 0B 1.9KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 2.0GiB 216B 578KiB 0B
nvim-headless 579MiB 216B 578KiB 0B
nvim-no-lsps 1.1GiB 216B 578KiB 0B
nvim-no-ts 2.1GiB 216B 578KiB 0B
nvim-small 1.3GiB 216B 578KiB 0B
# 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 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. # NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `vm` | 10GiB | 12MiB | 19KiB | 0B | # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 0B | 1.4MiB | 0B | | `docs` | 2.4MiB | 0B | 2.4MiB | 0B | | `docs-home-markdown` | 11KiB | 0B | 11KiB | 0B | | `docs-nixos-markdown` | 6.3KiB | 0B | 6.3KiB | 0B | | `docs-nvim-markdown` | 1.9KiB | 0B | 1.9KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 2.0GiB | 216B | 578KiB | 0B | | `nvim-headless` | 579MiB | 216B | 578KiB | 0B | | `nvim-no-lsps` | 1.1GiB | 216B | 578KiB | 0B | | `nvim-no-ts` | 2.1GiB | 216B | 578KiB | 0B | | `nvim-small` | 1.3GiB | 216B | 578KiB | 0B |
renovate force-pushed renovate/lock-file-maintenance from b1b3ff03e6 to 05a25ad2d3 2025-01-08 01:20:18 +01:00 Compare
forgejo-actions commented 2025-01-08 01:34:36 +01:00
First-time contributor
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 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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change
vm 10GiB 12MiB 19KiB 0B

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 0B 1.4MiB 0B
docs 2.4MiB 0B 2.4MiB 0B
docs-home-markdown 11KiB 0B 11KiB 0B
docs-nixos-markdown 6.3KiB 0B 6.3KiB 0B
docs-nvim-markdown 1.9KiB 0B 1.9KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 2.0GiB 216B 578KiB 0B
nvim-headless 579MiB 216B 578KiB 0B
nvim-no-lsps 1.1GiB 216B 578KiB 0B
nvim-no-ts 2.1GiB 216B 578KiB 0B
nvim-small 1.3GiB 216B 578KiB 0B
# 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 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. # NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `vm` | 10GiB | 12MiB | 19KiB | 0B | # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 0B | 1.4MiB | 0B | | `docs` | 2.4MiB | 0B | 2.4MiB | 0B | | `docs-home-markdown` | 11KiB | 0B | 11KiB | 0B | | `docs-nixos-markdown` | 6.3KiB | 0B | 6.3KiB | 0B | | `docs-nvim-markdown` | 1.9KiB | 0B | 1.9KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 2.0GiB | 216B | 578KiB | 0B | | `nvim-headless` | 579MiB | 216B | 578KiB | 0B | | `nvim-no-lsps` | 1.1GiB | 216B | 578KiB | 0B | | `nvim-no-ts` | 2.1GiB | 216B | 578KiB | 0B | | `nvim-small` | 1.3GiB | 216B | 578KiB | 0B |
renovate merged commit 05a25ad2d3 into main 2025-01-08 01:34:37 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
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/configuration.nix#234
No description provided.
Delete branch "renovate/lock-file-maintenance"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?