ci: add GH Ci to publish to crates.io #474

Merged
jalil merged 1 commit from jalil/publish-to-crates-io into main 2025-10-12 22:48:53 +02:00
Owner

This allows me to do trusted publishing.

This allows me to do trusted publishing.
jalil self-assigned this 2025-10-12 22:44:30 +02:00
ci: add GH Ci to publish to crates.io
All checks were successful
/ build (pull_request) Successful in 20s
/ checks (x86_64-linux, clippy) (pull_request) Successful in 12s
/ checks (x86_64-linux, deny) (pull_request) Successful in 3s
/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 32s
/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 30s
/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 32s
/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 29s
/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 31s
/ checks (x86_64-linux, nextest) (pull_request) Successful in 40s
/ checks (x86_64-linux, treefmt) (pull_request) Successful in 2s
/ trigger-release (pull_request) Successful in 19s
/ report-size (pull_request) Successful in 7s
/ build (push) Successful in 3s
/ checks (x86_64-linux, clippy) (push) Successful in 1s
/ checks (x86_64-linux, deny) (push) Successful in 1s
/ checks (x86_64-linux, module-ipv4-only-test) (push) Successful in 1s
/ checks (x86_64-linux, module-ipv4-test) (push) Successful in 1s
/ checks (x86_64-linux, module-ipv6-only-test) (push) Successful in 1s
/ checks (x86_64-linux, module-ipv6-test) (push) Successful in 1s
/ checks (x86_64-linux, module-nginx-test) (push) Successful in 1s
/ checks (x86_64-linux, nextest) (push) Successful in 1s
/ checks (x86_64-linux, treefmt) (push) Successful in 1s
/ trigger-release (push) Successful in 5s
/ report-size (push) Successful in 2s
867e69ad11
This allows me to do trusted publishing.

Signed-off-by: Jalil David Salamé Messina <jalil.salame@gmail.com>
jalil scheduled this pull request to auto merge when all checks succeed 2025-10-12 22:44:37 +02:00

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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change

Home Manager Configurations

Name Size Size Change NAR Size NAR Size Change

Packages

Name Size Size Change NAR Size NAR Size Change
webnsupdate 34MiB 0B 2.2MiB 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> ## NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| ## Home Manager Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `webnsupdate` | 34MiB | 0B | 2.2MiB | 0B |
jalil merged commit 867e69ad11 into main 2025-10-12 22:48:53 +02:00
jalil deleted branch jalil/publish-to-crates-io 2025-10-12 22:48:53 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
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/webnsupdate!474
No description provided.