jalil/webnsupdate
1
0
Fork 0
Code Issues 1 Pull requests 1 Releases Activity Actions

feat(renovate): enable lockFileMaintenance #36

Merged
jalil merged 2 commits from renovate-lockfile-maintenance into main 2024-12-29 18:50:30 +01:00
Conversation 3 Commits 2 Files changed 4 +53 -32
jalil commented 2024-12-29 17:43:44 +01:00
Owner
Copy link

This allows it to update the flake.lock and Cargo.lock files.

Also switch from a flake ref to a github ref as renovate cannot resolve flake refs.

This allows it to update the flake.lock and Cargo.lock files. Also switch from a flake ref to a github ref as renovate cannot resolve flake refs.
jalil self-assigned this 2024-12-29 17:43:44 +01:00
jalil added 1 commit 2024-12-29 17:43:44 +01:00
feat(renovate): enable lockFileMaintenance
Some checks failed
/ build (push) Successful in 2s
Details
/ check (push) Failing after 34s
Details
/ report-size (push) Successful in 8s
Details
e01ecb8f1b 
This allows it to update the flake.lock and Cargo.lock files.

Also switch from a flake ref to a github ref as renovate cannot resolve
flake refs.
forgejo-actions commented 2024-12-29 17:44:24 +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.

Packages

Name Size Size Change NAR Size NAR Size Change
cargo-update 1.4GiB 15MiB 848B 0B
default 35MiB 309KiB 2.8MiB 4.7KiB
git-cliff 60MiB 1.3MiB 19MiB 22KiB
webnsupdate 35MiB 309KiB 2.8MiB 4.7KiB
# 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 | |------|-----:|------------:|---------:|----------------:| | `cargo-update` | 1.4GiB | 15MiB | 848B | 0B | | `default` | 35MiB | 309KiB | 2.8MiB | 4.7KiB | | `git-cliff` | 60MiB | 1.3MiB | 19MiB | 22KiB | | `webnsupdate` | 35MiB | 309KiB | 2.8MiB | 4.7KiB |
jalil force-pushed renovate-lockfile-maintenance from e01ecb8f1b to 8b6c2ca462 2024-12-29 18:08:33 +01:00 Compare
jalil force-pushed renovate-lockfile-maintenance from 8b6c2ca462 to 2ba6277778 2024-12-29 18:09:00 +01:00 Compare
forgejo-actions commented 2024-12-29 18:09:26 +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.

Packages

Name Size Size Change NAR Size NAR Size Change
cargo-update 1.4GiB 15MiB 848B 0B
default 35MiB 309KiB 2.8MiB 4.7KiB
git-cliff 60MiB 1.3MiB 19MiB 22KiB
webnsupdate 35MiB 309KiB 2.8MiB 4.7KiB
# 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 | |------|-----:|------------:|---------:|----------------:| | `cargo-update` | 1.4GiB | 15MiB | 848B | 0B | | `default` | 35MiB | 309KiB | 2.8MiB | 4.7KiB | | `git-cliff` | 60MiB | 1.3MiB | 19MiB | 22KiB | | `webnsupdate` | 35MiB | 309KiB | 2.8MiB | 4.7KiB |
jalil added 1 commit 2024-12-29 18:37:02 +01:00
fix(flake): switch to github ref
All checks were successful
/ build (push) Successful in 1s
Details
/ check (push) Successful in 7s
Details
/ report-size (push) Successful in 2s
Details
6a1feb2612 
Switch from a flake ref to a github ref as renovate cannot resolve flake
refs, and they are slightly impure.

This shows some issues with the previous patch to the bind module which
we fix.
forgejo-actions commented 2024-12-29 18:37:15 +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.

Packages

Name Size Size Change NAR Size NAR Size Change
cargo-update 1.4GiB 15MiB 848B 0B
default 35MiB 309KiB 2.8MiB 4.7KiB
git-cliff 60MiB 1.3MiB 19MiB 22KiB
webnsupdate 35MiB 309KiB 2.8MiB 4.7KiB
# 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 | |------|-----:|------------:|---------:|----------------:| | `cargo-update` | 1.4GiB | 15MiB | 848B | 0B | | `default` | 35MiB | 309KiB | 2.8MiB | 4.7KiB | | `git-cliff` | 60MiB | 1.3MiB | 19MiB | 22KiB | | `webnsupdate` | 35MiB | 309KiB | 2.8MiB | 4.7KiB |
jalil merged commit 6a1feb2612 into main 2024-12-29 18:50:30 +01:00
jalil deleted branch renovate-lockfile-maintenance 2024-12-29 18:50:30 +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
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/webnsupdate#36
No description provided.
Delete branch "renovate-lockfile-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?