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

chore(config): migrate renovate config #332

Merged
jalil merged 1 commit from renovate/migrate-config into main 2025-03-09 21:39:31 +01:00
Conversation 2 Commits 1 Files changed 1 +1 -1
renovate commented 2025-03-09 12:40:21 +01:00
Collaborator
Copy link

The Renovate config in this repository needs migrating. Typically this is because one or more configuration options you are using have been renamed.

You don't need to merge this PR right away, because Renovate will continue to migrate these fields internally each time it runs. But later some of these fields may be fully deprecated and the migrations removed. So it's a good idea to merge this migration PR soon.

🔕 Ignore: Close this PR and you won't be reminded about config migration again, but one day your current config may no longer be valid.

❓ Got questions? Does something look wrong to you? Please don't hesitate to request help here.

This PR has been generated by Renovate Bot.

The Renovate config in this repository needs migrating. Typically this is because one or more configuration options you are using have been renamed. You don't need to merge this PR right away, because Renovate will continue to migrate these fields internally each time it runs. But later some of these fields may be fully deprecated and the migrations removed. So it's a good idea to merge this migration PR soon. 🔕 **Ignore**: Close this PR and you won't be reminded about config migration again, but one day your current config may no longer be valid. ❓ Got questions? Does something look wrong to you? Please don't hesitate to [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
renovate added 1 commit 2025-03-09 12:40:21 +01:00
chore(config): migrate config .renovaterc.json
All checks were successful
/ check (nvimDev) (push) Successful in 6s
Details
/ check (nvimHeadless) (push) Successful in 2s
Details
/ check (nvimNoBundledBins) (push) Successful in 5s
Details
/ check (nvimNoLsp) (push) Successful in 5s
Details
/ check (nvimNoTSGrammars) (push) Successful in 5s
Details
/ check (treefmt) (push) Successful in 3s
Details
/ check-renovaterc (push) Successful in 2s
Details
/ build (audiomenu) (push) Successful in 1s
Details
/ build (docs) (push) Successful in 2s
Details
/ build (jpassmenu) (push) Successful in 1s
Details
/ build (nixosConfigurations.vm.config.system.build.toplevel) (push) Successful in 16s
Details
/ build (nvim) (push) Successful in 9s
Details
/ report-size (push) Successful in 1m2s
Details
0df6f76b00
jalil was assigned by renovate 2025-03-09 12:40:21 +01:00
jalil scheduled this pull request to auto merge when all checks succeed 2025-03-09 12:41:15 +01:00
forgejo-actions commented 2025-03-09 12:50:05 +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 8.8GiB 0B 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 2.2KiB 0B 2.2KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 1.4GiB 0B 578KiB 0B
nvim-headless 389MiB 0B 578KiB 0B
nvim-no-lsps 929MiB 0B 578KiB 0B
nvim-no-ts 1.5GiB 0B 578KiB 0B
nvim-small 1.1GiB 0B 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` | 8.8GiB | 0B | 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` | 2.2KiB | 0B | 2.2KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 1.4GiB | 0B | 578KiB | 0B | | `nvim-headless` | 389MiB | 0B | 578KiB | 0B | | `nvim-no-lsps` | 929MiB | 0B | 578KiB | 0B | | `nvim-no-ts` | 1.5GiB | 0B | 578KiB | 0B | | `nvim-small` | 1.1GiB | 0B | 578KiB | 0B |
jalil scheduled this pull request to auto merge when all checks succeed 2025-03-09 21:36:39 +01:00
jalil scheduled this pull request to auto merge when all checks succeed 2025-03-09 21:37:19 +01:00
jalil force-pushed renovate/migrate-config from 0df6f76b00 to 5fe3e70149 2025-03-09 21:37:28 +01:00 Compare
forgejo-actions commented 2025-03-09 21:39:29 +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 8.8GiB 0B 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 2.2KiB 0B 2.2KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 1.4GiB 0B 578KiB 0B
nvim-headless 389MiB 0B 578KiB 0B
nvim-no-lsps 929MiB 0B 578KiB 0B
nvim-no-ts 1.5GiB 0B 578KiB 0B
nvim-small 1.1GiB 0B 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` | 8.8GiB | 0B | 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` | 2.2KiB | 0B | 2.2KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 1.4GiB | 0B | 578KiB | 0B | | `nvim-headless` | 389MiB | 0B | 578KiB | 0B | | `nvim-no-lsps` | 929MiB | 0B | 578KiB | 0B | | `nvim-no-ts` | 1.5GiB | 0B | 578KiB | 0B | | `nvim-small` | 1.1GiB | 0B | 578KiB | 0B |
jalil merged commit 5fe3e70149 into main 2025-03-09 21:39:31 +01:00
jalil deleted branch renovate/migrate-config 2025-03-09 21:39:31 +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
jalil
3 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#332
No description provided.
Delete branch "renovate/migrate-config"

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?