Fix publishing on crates.io #472

Merged

jalil merged 2 commits from push-tvmukwtumkqk into main 2025-10-12 22:19:20 +02:00

Conversation 1 Commits 2 Files changed 2 +7 -6

jalil commented 2025-10-12 21:50:54 +02:00

Owner

Copy link

There were some issues that prevented us from publishing to crates.io

There were some issues that prevented us from publishing to crates.io

jalil added the

bug

label 2025-10-12 21:50:54 +02:00

jalil self-assigned this 2025-10-12 21:50:54 +02:00

jalil added 2 commits 2025-10-12 21:50:54 +02:00

fix: allow publishing to crates.io ... 7c2970939a

Needs to be specified as a registry.

Signed-off-by: Jalil David Salamé Messina <jalil.salame@gmail.com>

fix: remove categories ... e4e63372d0

None of the supported categories seem to fit:
https://crates.io/category_slugs

Signed-off-by: Jalil David Salamé Messina <jalil.salame@gmail.com>

jalil force-pushed push-tvmukwtumkqk from e4e63372d0 to 19d7dc1b7f 2025-10-12 21:53:20 +02:00 Compare

forgejo-actions commented 2025-10-12 21:54:57 +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.

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 scheduled this pull request to auto merge when all checks succeed 2025-10-12 21:56:06 +02:00

jalil force-pushed push-tvmukwtumkqk from 19d7dc1b7f to 68416dfd31 2025-10-12 22:06:19 +02:00 Compare

jalil scheduled this pull request to auto merge when all checks succeed 2025-10-12 22:06:30 +02:00

jalil force-pushed push-tvmukwtumkqk from 68416dfd31 to 4d8e761aa7 2025-10-12 22:11:54 +02:00 Compare

jalil force-pushed push-tvmukwtumkqk from 4d8e761aa7 to f6f1f3bddd 2025-10-12 22:13:55 +02:00 Compare

jalil force-pushed push-tvmukwtumkqk from f6f1f3bddd to b72fcbaf87 2025-10-12 22:18:05 +02:00 Compare

jalil merged commit b72fcbaf87 into main 2025-10-12 22:19:20 +02:00

jalil deleted branch push-tvmukwtumkqk 2025-10-12 22:19:20 +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

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!472

No description provided.