chore(config): migrate renovate config #144

Merged

jalil merged 1 commit from renovate/migrate-config into main 2025-03-10 20:19:30 +01:00

Conversation 2 Commits 1 Files changed 1 +1 -1

renovate commented 2025-03-09 21:50:26 +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 21:50:26 +01:00

chore(config): migrate config .renovaterc.json ca0581cc3c

jalil was assigned by renovate 2025-03-09 21:50:26 +01:00

forgejo-actions commented 2025-03-09 21:53:08 +01: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 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	35MiB	0B	2.9MiB	0B
git-cliff	60MiB	0B	19MiB	0B
webnsupdate	35MiB	0B	2.9MiB	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. # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 35MiB | 0B | 2.9MiB | 0B | | `git-cliff` | 60MiB | 0B | 19MiB | 0B | | `webnsupdate` | 35MiB | 0B | 2.9MiB | 0B |

jalil force-pushed renovate/migrate-config from ca0581cc3c to 4cdffc20bc 2025-03-10 08:09:26 +01:00 Compare

forgejo-actions commented 2025-03-10 08:14:40 +01: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 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	35MiB	0B	2.9MiB	0B
git-cliff	60MiB	0B	19MiB	0B
webnsupdate	35MiB	0B	2.9MiB	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. # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 35MiB | 0B | 2.9MiB | 0B | | `git-cliff` | 60MiB | 0B | 19MiB | 0B | | `webnsupdate` | 35MiB | 0B | 2.9MiB | 0B |

jalil merged commit 4cdffc20bc into main 2025-03-10 20:19:30 +01:00

jalil deleted branch renovate/migrate-config 2025-03-10 20:19:30 +01:00

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

3 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!144

No description provided.