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

ci: fix release-plz #394

Merged
jalil merged 1 commit from push-tkwsmzlollwl into main 2025-08-29 17:01:29 +02:00
Conversation 1 Commits 1 Files changed 1 +14 -10
jalil commented 2025-08-29 08:10:50 +02:00
Owner
Copy link

Version v0.3.6 had nightly features in the Cargo.toml, these were stripped on build, but kept when the release was generated.

Version v0.3.6 had nightly features in the `Cargo.toml`, these were stripped on build, but kept when the release was generated.
jalil self-assigned this 2025-08-29 08:10:50 +02:00
ci: fix release-plz
Some checks failed
/ build (pull_request) Successful in 3s
Details
/ checks (x86_64-linux, clippy) (pull_request) Successful in 3s
Details
/ checks (x86_64-linux, deny) (pull_request) Successful in 3s
Details
/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 6s
Details
/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 6s
Details
/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 6s
Details
/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 6s
Details
/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 6s
Details
/ checks (x86_64-linux, nextest) (pull_request) Successful in 3s
Details
/ checks (x86_64-linux, treefmt) (pull_request) Successful in 3s
Details
/ trigger-release (pull_request) Failing after 5s
Details
/ report-size (pull_request) Successful in 10s
Details
55a7d30a99
 
Version v0.3.6 had nightly features in the `Cargo.toml`, these were
stripped on build, but kept when the release was generated.
forgejo-actions commented 2025-08-29 08:11:48 +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 35MiB 0B 3.0MiB 0B
git-cliff 61MiB 0B 20MiB 0B
webnsupdate 35MiB 0B 3.0MiB 0B
<!-- 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` | 35MiB | 0B | 3.0MiB | 0B | | `git-cliff` | 61MiB | 0B | 20MiB | 0B | | `webnsupdate` | 35MiB | 0B | 3.0MiB | 0B |
jalil force-pushed push-tkwsmzlollwl from 55a7d30a99 to 585b0c2e1c 2025-08-29 09:20:55 +02:00 Compare
jalil force-pushed push-tkwsmzlollwl from 585b0c2e1c to dc51eebbd7 2025-08-29 16:46:37 +02:00 Compare
jalil force-pushed push-tkwsmzlollwl from dc51eebbd7 to 59f024f21d 2025-08-29 16:50:24 +02:00 Compare
jalil force-pushed push-tkwsmzlollwl from 59f024f21d to 5e2bcfbb70 2025-08-29 16:54:33 +02:00 Compare
jalil force-pushed push-tkwsmzlollwl from 5e2bcfbb70 to 9773c3a024 2025-08-29 16:58:08 +02:00 Compare
jalil force-pushed push-tkwsmzlollwl from 9773c3a024 to 1e96625ec8 2025-08-29 17:00:12 +02:00 Compare
jalil merged commit 1e96625ec8 into main 2025-08-29 17:01:29 +02:00
jalil deleted branch push-tkwsmzlollwl 2025-08-29 17:01:29 +02: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
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#394
No description provided.
Delete branch "push-tkwsmzlollwl"

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?